http://bugs.winehq.org/show_bug.cgi?id=19219 Jeff Zaroyko <jeffz(a)jeffz.name> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |taedium_vitae(a)eml.cc maniac <jedimastermaniac(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jedimastermaniac(a)hotmail.co | |m Tim Burrell <tim(a)timburrell.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tim(a)timburrell.net Francesco Munda <syylk(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |syylk(a)hotmail.com --- Comment #36 from Jeff Zaroyko <jeffz(a)jeffz.name> 2009-07-28 02:45:41 --- *** Bug 19485 has been marked as a duplicate of this bug. *** --- Comment #37 from maniac <jedimastermaniac(a)hotmail.com> 2009-07-28 20:32:07 --- Could it be possible that the latest crash were caused due to bad nvidia drivers? I see almost everyone with this problem had version 185.18 The problem seemed to persist even in versions when wine used to work wine 1.20 doesnt work either for me for example when everything was alright. I haven't test the new 190.18 beta drivers but i will. Anyone who might have time to do so should have a look too --- Comment #38 from DL <taedium_vitae(a)eml.cc> 2009-07-28 20:47:11 --- This bug also occurs with The Witcher. --- Comment #39 from N3o <diafoirus(a)gmail.com> 2009-07-28 21:49:22 --- (In reply to comment #37)
Could it be possible that the latest crash were caused due to bad nvidia drivers? I see almost everyone with this problem had version 185.18 The problem seemed to persist even in versions when wine used to work wine 1.20 doesnt work either for me for example when everything was alright.
I haven't test the new 190.18 beta drivers but i will. Anyone who might have time to do so should have a look too
Yes, is possible, we have a recent history about a bug in old nVidia 180.x driver aprox and fixed in 185.x, I'll test with the last beta too, --- Comment #40 from N3o <diafoirus(a)gmail.com> 2009-07-28 21:58:56 --- More info about 190.18 beta driver + download link : 32bits: http://www.nvidia.com/object/linux_display_ia32_190.18.html 64bits: http://www.nvidia.com/object/linux_display_amd64_190.18.html --- Comment #41 from DL <taedium_vitae(a)eml.cc> 2009-07-28 22:07:54 --- I've tested with 180.60/185.18.14/185.18.29/190.16 and 190.18 and the crash still occurs with all of these drivers.The 190.X series also introduces another bug with the witcher that results in streams coming out of the heads and shoulders of characters in the game. --- Comment #42 from hpestilence <hpestilence(a)gmail.com> 2009-07-29 02:24:40 --- I have the crash with my ATI card too so it's not nvidia only. --- Comment #43 from Tim Burrell <tim(a)timburrell.net> 2009-07-29 08:43:04 --- I confirm that this happens to me as well w/ 1.1.25, and 1.1.26. I just downgraded to 1.1.24 and the crash is no longer present. --- Comment #44 from Caladan <a.vankaam(a)chello.nl> 2009-07-29 09:43:44 --- (In reply to comment #37)
Could it be possible that the latest crash were caused due to bad nvidia drivers? I see almost everyone with this problem had version 185.18 The problem seemed to persist even in versions when wine used to work wine 1.20 doesnt work either for me for example when everything was alright.
I haven't test the new 190.18 beta drivers but i will. Anyone who might have time to do so should have a look too
absolutely no problem with wine 1.1.24 and the same nvidia drivers, I did a local 1.1.24 install and every now and then will try the current git, on the 1.1.24 no crash at all, on the current git a crash within no time, so in that respect it's not nvidia driver related. might be the change in wine made it a bit stricter on some things thus displaying a driver bug or might just be the change in wine holds an error, but well I can't tell as that is beyond me --- Comment #45 from DL <taedium_vitae(a)eml.cc> 2009-07-29 20:33:32 --- This also creates a glitch in Call of Duty 4, where the screen flickers excessively.This is not refresh rate flicker, or tearing, it's like a black image partially covering the screen and flickering every second or so.The glitch disappears when the 2 commits are removed. --- Comment #46 from Francesco Munda <syylk(a)hotmail.com> 2009-07-31 16:56:08 --- Kernel: 2.6.30-gentoo-r2 #1 SMP PREEMPT CPU: i686 AMD Phenom(tm) 9500 Quad-Core Processor GPU: nvidia GeForce 8800 GT/256 Drivers: nvidia 180.60 (so not the in/famous 185.x or 190.x) Same problem as OP. It seems to be more frequent when changing session (undocking/docking/swapping ships/jumping) and when generating player portraits. Removed bad commits as per hpestilence's comment #16 and the page faulting crashes disappear. As if NTDLL now frees some resources when it souldn't, or right before it's safe to do so. --- Comment #47 from Alexandre Julliard <julliard(a)winehq.org> 2009-08-04 13:16:29 --- Created an attachment (id=22807) --> (http://bugs.winehq.org/attachment.cgi?id=22807) Don't release low memory. Apparently these apps are built with the large address aware flag to indicate they support addresses >2Gb, but they import d3dx9 which doesn't. This patch should hopefully hide the bug again. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.