http://bugs.winehq.org/show_bug.cgi?id=19219
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |taedium_vitae@eml.cc
maniac jedimastermaniac@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jedimastermaniac@hotmail.co | |m
Tim Burrell tim@timburrell.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |tim@timburrell.net
Francesco Munda syylk@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |syylk@hotmail.com
Bob bob+wine@mcelrath.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bob+wine@mcelrath.org
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED Status|RESOLVED |CLOSED
drachu@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |drachu@gmail.com
Joachim Rousseau syrion.com@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |syrion.com@gmail.com
--- Comment #36 from Jeff Zaroyko jeffz@jeffz.name 2009-07-28 02:45:41 CDT --- *** Bug 19485 has been marked as a duplicate of this bug. ***
--- Comment #37 from maniac jedimastermaniac@hotmail.com 2009-07-28 20:32:07 CDT --- 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 dredgingthelake@gmail.com 2009-07-28 20:47:11 CDT --- This bug also occurs with The Witcher.
--- Comment #39 from N3o diafoirus@gmail.com 2009-07-28 21:49:22 CDT --- (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@gmail.com 2009-07-28 21:58:56 CDT --- 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 dredgingthelake@gmail.com 2009-07-28 22:07:54 CDT --- 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@gmail.com 2009-07-29 02:24:40 CDT --- I have the crash with my ATI card too so it's not nvidia only.
--- Comment #43 from Tim Burrell tim@timburrell.net 2009-07-29 08:43:04 CDT --- 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@chello.nl 2009-07-29 09:43:44 CDT --- (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 dredgingthelake@gmail.com 2009-07-29 20:33:32 CDT --- 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@hotmail.com 2009-07-31 16:56:08 CDT --- 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@winehq.org 2009-08-04 13:16:29 CDT --- 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.
--- Comment #48 from Bob bob+wine@mcelrath.org 2009-08-04 18:45:42 CDT --- This new patch seems to work (applied to git head). Top still shows
PID PPID USER NI VIRT SWAP RES SHR S P %CPU TIME COMMAND 13188 1 <user> 0 1946m 1.0g 932m 37m R 1 101 175:04 C:\Games\EVE Online\bin\ExeFile.exe
which I still find suspicious. (e.g. 1.0g swap is claimed but only 17M is actually being used) Previously it was claiming 4G however, so it's an improvement, and so far I haven't seen the random crash.
I did see the crash at the login character selection screen once, which I think is a different problem.
--- Comment #49 from hpestilence hpestilence@gmail.com 2009-08-04 21:28:37 CDT --- It looks like it is working, been playing EVE Online for almost 4 hours and no crashes. I'm using the latest git + patch. Memory started at around 1.7 gigs and is currently at 1.9 according to top.
--- Comment #50 from DL dredgingthelake@gmail.com 2009-08-04 21:51:42 CDT --- The witcher no longer crashes, either.
--- Comment #51 from Rico kgbricola@web.de 2009-08-05 15:03:02 CDT --- The patch (commit http://source.winehq.org/git/wine.git/?a=commit; h=c10bdbefd69786846b035d1c38de3052bed67875 ) fixes Gothic3, too.
--- Comment #52 from Alexandre Julliard julliard@winehq.org 2009-08-06 10:23:54 CDT --- Marking fixed then.
--- Comment #53 from Alexandre Julliard julliard@winehq.org 2009-08-07 12:52:03 CDT --- Closing bugs fixed in 1.1.2,7.
--- Comment #54 from drachu@gmail.com 2009-08-24 17:03:58 CDT --- Created an attachment (id=23241) --> (http://bugs.winehq.org/attachment.cgi?id=23241) dump of crash on version 1.1.28
--- Comment #55 from drachu@gmail.com 2009-08-24 17:05:51 CDT --- Created an attachment (id=23242) --> (http://bugs.winehq.org/attachment.cgi?id=23242) dump of crash on version 1.1.28
--- Comment #56 from drachu@gmail.com 2009-08-24 17:13:25 CDT --- Hi,
I can confirm that this bug first time happened for me on version 1.1.25, eve have started quite frequently crashing at random moments. When Wine updated into 1.1.27 crashes still occurred but not as frequently as previously (I could play for few hours on both accounts). This was somehow weird because everyone else reported 1.1.27 as working and this bug was closed. So I waited till version 1.1.28 and checked it again. On my computer, Eve once again crashes like crazy, I've attached trace (sorry for double post). Sometimes I'm not even able to log on my account. Sometimes it crashes after 30minutes of playing.
Could someone compare my trace and 1.1.26 trace of EVE and confirm that it's the same error (for me it is, but im not professional), and probably reopen this bug.
Thank you in advance.
--- Comment #57 from Vitaliy Margolen vitaliy-bugzilla@kievinfo.com 2009-08-24 23:06:50 CDT --- (In reply to comment #56) Why did you attached the same backtrace twice? As a tar with one file??? With WINEDEBUG set??? DO NOT DO THAT!
This bug is closed, if you have any other crashes open a new bug, DO NOT USE WINEDEBUG flags unless explicitly asked for.
--- Comment #58 from drachu@gmail.com 2009-08-26 02:07:17 CDT --- Why did you attached the same backtrace twice? === I said sorry for double posting. Not my fault winehq.orgs responds very clumsy (sometimes).
As a tar with one file??? With WINEDEBUG set??? DO NOT DO THAT! === I don't know what are you talking about. I thought it's a way I should provide trace.
This bug is closed, if you have any other crashes open a new bug, DO NOT USE WINEDEBUG flags unless explicitly asked for. === So I should start new bug that is clone of this bug with exactly the same description, back traces and all? I don't think it's very smart idea, what is more I think that's why there was implemented feature called 'reopening'.
--- Comment #59 from Joachim Rousseau syrion.com@gmail.com 2009-08-26 08:43:44 CDT --- (In reply to comment #58)
This bug is closed, if you have any other crashes open a new bug, DO NOT USE WINEDEBUG flags unless explicitly asked for. === So I should start new bug that is clone of this bug with exactly the same description, back traces and all? I don't think it's very smart idea, what is more I think that's why there was implemented feature called 'reopening'.
If you read the history, you can understand that the bug is fixed. You trace is *not* the trace of this bug but the trace of a new one. This one had been fixed (I have no crash anymore, even with nvidia, and I'm not the only one). The fact people have no problem anymore and you do proves you had another one. And more, as you didn't traced correctly, your trace may not be a consequence of this bug but a lot of things. It may not be correlated with the problem you experience.
Fill in a new bug if you are sur or use forums.
--- Comment #60 from drachu@gmail.com 2009-08-26 18:16:14 CDT --- Hi,
Thank you for some more explanation. However my bug have many common similarities with original reported. It was introduced with 1.1.25 version of wine. It was introduced by changes on ntdlll.
Of course we can assume that original bug was fixed, we can assume that this regression is driven by patching previous regression. But in fact if I will start bisecting it will show that the bug was introduced by very the same change in the wine as original bug. So what next?
I personally think that changes into ntdll was not solved everywhere, I think it was solved in majority of the cases. But Im not in the majority.
So I would like to know, what I should do after starting a new bug, as mr. Vitality said that im nooblet because of posting tar file with backtrace nobody asked in bug that does not exists and for me it's just bad karma.
P.S.
But if you ask I can start bisecting once again, not a problem for me.