[Bug 19219] New: EVE crashes with a page fault after update to WINE 1.1.25
http://bugs.winehq.org/show_bug.cgi?id=19219 Summary: EVE crashes with a page fault after update to WINE 1.1.25 Product: Wine Version: 1.1.25 Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P1 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: sven.dack(a)ntlworld.com After updating WINE from version 1.1.24 to 1.1.25 does EVE crash with a page fault. It happens after about 1-5 minutes during the game and without any sign to what might cause. Hardware:AMD Phenom x4 9850 BE with NVidia GTX 260 GFX Driver: NVidia 185.18.14 Kernel: 2.6.26 Distribution: Debian Lenny/Squeeze See the attachment for the WINE output. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 --- Comment #1 from Sven Dack <sven.dack(a)ntlworld.com> 2009-07-06 07:43:12 --- Created an attachment (id=22218) --> (http://bugs.winehq.org/attachment.cgi?id=22218) WINE output -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 Sven Dack <sven.dack(a)ntlworld.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #22218|application/octet-stream |text/plain mime type| | -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 Laissus Yoann <cyberyoyo21(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cyberyoyo21(a)hotmail.com --- Comment #2 from Laissus Yoann <cyberyoyo21(a)hotmail.com> 2009-07-06 07:49:51 --- You will need to run a regression test to determine which patch produces this crash. http://wiki.winehq.org/RegressionTesting -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 --- Comment #3 from Sven Dack <sven.dack(a)ntlworld.com> 2009-07-06 08:02:30 --- No, I do not have the time. I now went back to 1.1.24. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 Vitaliy Margolen <vitaliy(a)kievinfo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression Priority|P1 |P2 Summary|EVE crashes with a page |EVE crashes with a page |fault after update to WINE |fault |1.1.25 | -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |DUPLICATE --- Comment #4 from Austin English <austinenglish(a)gmail.com> 2009-07-06 11:24:36 --- Dupe *** This bug has been marked as a duplicate of bug 19217 *** -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 Sven Dack <sven.dack(a)ntlworld.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|DUPLICATE | --- Comment #5 from Sven Dack <sven.dack(a)ntlworld.com> 2009-07-06 12:26:19 --- I have no graphical glitches nor do I get the same output as described in 19217. How is this a duplicate? The fact that it crashes in both cases hardly qualifies for calling it a duplicate. It would be a duplicate to almost any other bug. It appears that 19217 describes two problems as one. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 --- Comment #6 from Austin English <austinenglish(a)gmail.com> 2009-07-06 13:08:22 --- (In reply to comment #5)
I have no graphical glitches nor do I get the same output as described in 19217.
How is this a duplicate?
The fact that it crashes in both cases hardly qualifies for calling it a duplicate. It would be a duplicate to almost any other bug.
It appears that 19217 describes two problems as one.
Both bugs have crashes in 1.1.25, but not 1.1.24. Neither of you has done a regression test, so until there are two different results, the bug could very well be the same. Still need the regression test... -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 --- Comment #7 from Sven Dack <sven.dack(a)ntlworld.com> 2009-07-06 13:27:05 --- Possible, but you first have to prove it to be a duplicate. What makes it worse is that by only closing bug reports you are only ignoring bugs, but you have not found them nor have you fixed them. I have my own software and bugs to work on. So I cannot do any more regression testing than to test it with two different releases. Why do you not do the regression test? -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 --- Comment #8 from Austin English <austinenglish(a)gmail.com> 2009-07-06 13:45:23 --- (In reply to comment #7)
Possible, but you first have to prove it to be a duplicate. What makes it worse is that by only closing bug reports you are only ignoring bugs, but you have not found them nor have you fixed them.
I have my own software and bugs to work on. So I cannot do any more regression testing than to test it with two different releases.
You reported the bug. The burden is on you to provide the needed information.
Why do you not do the regression test?
I don't have the software nor time/interest to follow this bug. I have other wine bugs to fix/tests to run/things to do. If you expect this bug to be fixed, then you need to provide the needed information. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 --- Comment #9 from Sven Dack <sven.dack(a)ntlworld.com> 2009-07-06 14:24:24 --- I suggest to fix the bug when you have more time and interest. Until then will I stop reporting bugs. You seem to be very busy. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 Vitaliy Margolen <vitaliy(a)kievinfo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |ABANDONED --- Comment #10 from Vitaliy Margolen <vitaliy(a)kievinfo.com> 2009-07-06 20:39:08 --- If you can not be bothered to perform simple regression testing, don't bother reporting bugs at all. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 Vitaliy Margolen <vitaliy(a)kievinfo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #11 from Vitaliy Margolen <vitaliy(a)kievinfo.com> 2009-07-06 20:40:02 --- Closing. When you get desire to help Wine, you are very welcome to do so. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 Sven Dack <sven.dack(a)ntlworld.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |UNCONFIRMED Resolution|ABANDONED | --- Comment #12 from Sven Dack <sven.dack(a)ntlworld.com> 2009-07-06 21:35:45 --- Reopened. My desire to help and the time that I have available are not the same. In the meantime, please, talk to Juliard. I have send him an e-mail regarding your attitude of how you handle bug reports. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 Vitaliy Margolen <vitaliy(a)kievinfo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |ABANDONED --- Comment #13 from Vitaliy Margolen <vitaliy(a)kievinfo.com> 2009-07-07 07:50:06 --- Regression test results are where? When you have them on your hand, reopen. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 Vitaliy Margolen <vitaliy(a)kievinfo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #14 from Vitaliy Margolen <vitaliy(a)kievinfo.com> 2009-07-07 07:50:51 --- Closing -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 --- Comment #15 from Sven Dack <sven.dack(a)ntlworld.com> 2009-07-07 08:13:58 --- No, I told Juliard I would look into it in a few weeks, but with your attitude can I not be bothered, seriously. I am on holiday. Fix your bugs yourself. I will see how you much you have progressed with 1.1.25. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 hpestilence <hpestilence(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hpestilence(a)gmail.com, | |julliard(a)winehq.org --- Comment #16 from hpestilence <hpestilence(a)gmail.com> 2009-07-10 00:46:24 --- I found the commit that causes this 09712593c8496be5e952b7316099f9eed5043203 is first bad commit commit 09712593c8496be5e952b7316099f9eed5043203 Author: Alexandre Julliard <julliard at winehq.org> Date: Thu Jun 25 14:18:53 2009 +0200 ntdll: Release some address space after the process initialization is done. I had to revert commit 1ac7576d477a6f22fa6d5758db6d8344d4bad1a9 ntdll: Disable releasing the address space on Mac OS since dyld doesn't support this. also in order to revert the first commit. Then I compiled the latest git and eve-online is running fine. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 hpestilence <hpestilence(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever Confirmed|0 |1 --- Comment #17 from hpestilence <hpestilence(a)gmail.com> 2009-07-10 04:00:42 --- *** This bug has been confirmed by popular vote. *** -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 Ken Sharp <kennybobs(a)o2.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jms.lambert(a)googlemail.com --- Comment #18 from Ken Sharp <kennybobs(a)o2.co.uk> 2009-07-10 16:09:24 --- *** Bug 19271 has been marked as a duplicate of this bug. *** -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 Ken Sharp <kennybobs(a)o2.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Resolution|ABANDONED | --- Comment #19 from Ken Sharp <kennybobs(a)o2.co.uk> 2009-07-10 16:11:16 --- Bisect done, reopening. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 Chad Simmons <chad.simmons(a)member.fsf.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |chad.simmons(a)member.fsf.org --- Comment #20 from Chad Simmons <chad.simmons(a)member.fsf.org> 2009-07-10 18:44:59 --- Verified reverting the patches mentioned above resolves the issue in the current GIT tree. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 Rico <kgbricola(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |10778 --- Comment #21 from Rico <kgbricola(a)web.de> 2009-07-11 07:46:47 --- Gothic 3 suffers from the same regression. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 N3o <diafoirus(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |diafoirus(a)gmail.com --- Comment #22 from N3o <diafoirus(a)gmail.com> 2009-07-11 12:03:53 --- Confirming bug and reverting the patches mentioned above resolves the issue in the current GIT tree. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 --- Comment #23 from Alexandre Julliard <julliard(a)winehq.org> 2009-07-13 08:46:28 --- Please try to get a +virtual,+seh trace. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 --- Comment #24 from Rico <kgbricola(a)web.de> 2009-07-13 10:28:26 --- Created an attachment (id=22355) --> (http://bugs.winehq.org/attachment.cgi?id=22355) Gothic3: +virtual,+seh log This is a log from a gothic 3 run with +virtual,+seh. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 --- Comment #25 from Adam <gnuman1(a)gmail.com> 2009-07-14 18:28:22 --- Created an attachment (id=22380) --> (http://bugs.winehq.org/attachment.cgi?id=22380) Wine 1.1.25 seh,virtual log Crash log for Eve is attached with WINEDBG=virtual,seh -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 Adam <gnuman1(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #22380|Wine 1.1.25 seh,virtual log |Wine 1.1.25 seh,virtual log description| | | |in Eve -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 Ken Sharp <kennybobs(a)o2.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |a.vankaam(a)chello.nl --- Comment #26 from Ken Sharp <kennybobs(a)o2.co.uk> 2009-07-15 09:37:50 --- *** Bug 19221 has been marked as a duplicate of this bug. *** -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 Ken Sharp <kennybobs(a)o2.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEW Component|-unknown |ntdll --- Comment #27 from Ken Sharp <kennybobs(a)o2.co.uk> 2009-07-15 09:39:28 --- Confirming. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 --- Comment #28 from Caladan <a.vankaam(a)chello.nl> 2009-07-15 11:13:45 --- Created an attachment (id=22385) --> (http://bugs.winehq.org/attachment.cgi?id=22385) lord of the rings online - crash with 1.1.25 Since bug 19219 has been marked a duplicate of this one, here is a +virtual,+seh trace for lord of the rings online, it crashed this time the moment I logged it. last line in the log is trace:virtual:NtFreeVirtualMemory 0xffffffff 0x470000 00000000 8000 Hope this helps. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 joneill(a)escom.us changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joneill(a)escom.us -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 Thomas Kowaliczek <linuxdonald(a)linuxdonald.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |linuxdonald(a)linuxdonald.de --- Comment #29 from Thomas Kowaliczek <linuxdonald(a)linuxdonald.de> 2009-07-17 18:22:01 --- the problem is to in wine 1.1.26 :( -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 Thomas Kowaliczek <linuxdonald(a)linuxdonald.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |linuxdonald(a)linuxdonald.de --- Comment #29 from Thomas Kowaliczek <linuxdonald(a)linuxdonald.de> 2009-07-17 18:22:01 --- the problem is to in wine 1.1.26 :( --- Comment #30 from Thomas Kowaliczek <linuxdonald(a)linuxdonald.de> 2009-07-17 18:22:34 --- the problem is too in wine 1.1.26 :( -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 --- Comment #31 from N3o <diafoirus(a)gmail.com> 2009-07-18 23:31:17 --- Confirming in 1.1.26 -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 Miro Stoyanov <mkstoyanov(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mkstoyanov(a)hotmail.com --- Comment #32 from Miro Stoyanov <mkstoyanov(a)hotmail.com> 2009-07-19 09:25:48 --- Same commit "commit 09712593c8496be5e952b7316099f9eed5043203" give trouble for a custom mod on Civilization IV Beyond the Sword v3.19 Regular Civ IV BtS and mods work, but my custom mod fails with error "Cannot load shared libraries". About 50 people play the mod under windows and there are no problems and I have no problems with several good git bisects. The mod can be found at http://forums.civfanatics.com/showthread.php?t=295451 (in case anyone is interested in testing this). I have not observed any problems with Starcraft, Warcraft III, Heroes of Might and Magic V. I can post extra details if needed. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 waveclaw <waveclaw(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |waveclaw(a)hotmail.com --- Comment #33 from waveclaw <waveclaw(a)hotmail.com> 2009-07-19 21:55:51 --- EVE crashes with a page fault. This also happened on 1.1.25 quite frequently. Did not happen with 1.1.24 Hardware:AMD Phenom 9550 Quad-core with 2x NVidia GTX 8600GT in SLI GFX Driver: NVidia 185.18.14 Pulse Audio: 0.9.15 Alsa: 1.0.18 Kernel: 2.6.27.23-0.1-default Distribution: openSuSE 11.1 x86_64 wine: 1.1.26 from distribution RPM (RPM Vendor: openSUSE Build Service, Release: 1.1, Build Date: Fri 17 Jul 2009 08:06:47 PM CDT) Command: aoss wine explorer /desktop=EVE2,800x600 "C:\Program Files\CCP\EVE\eve.exe" +virtual,+seh See attached backtrace and edited log -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 waveclaw <waveclaw(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |waveclaw(a)hotmail.com --- Comment #33 from waveclaw <waveclaw(a)hotmail.com> 2009-07-19 21:55:51 --- EVE crashes with a page fault. This also happened on 1.1.25 quite frequently. Did not happen with 1.1.24 Hardware:AMD Phenom 9550 Quad-core with 2x NVidia GTX 8600GT in SLI GFX Driver: NVidia 185.18.14 Pulse Audio: 0.9.15 Alsa: 1.0.18 Kernel: 2.6.27.23-0.1-default Distribution: openSuSE 11.1 x86_64 wine: 1.1.26 from distribution RPM (RPM Vendor: openSUSE Build Service, Release: 1.1, Build Date: Fri 17 Jul 2009 08:06:47 PM CDT) Command: aoss wine explorer /desktop=EVE2,800x600 "C:\Program Files\CCP\EVE\eve.exe" +virtual,+seh See attached backtrace and edited log --- Comment #34 from waveclaw <waveclaw(a)hotmail.com> 2009-07-19 21:57:17 --- Created an attachment (id=22464) --> (http://bugs.winehq.org/attachment.cgi?id=22464) Wine 1.1.26 backtrace in Eve Backtrace per http://wiki.winehq.org/Backtraces for crash in Eve-Online for wine 1.1.26 -- 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.
http://bugs.winehq.org/show_bug.cgi?id=19219 --- Comment #35 from waveclaw <waveclaw(a)hotmail.com> 2009-07-19 21:59:37 --- Created an attachment (id=22465) --> (http://bugs.winehq.org/attachment.cgi?id=22465) wine 1.1.26 log for Eve-Online crash Matching logfile for Eve-Online crash in wine 1.1.26. +160,000 lines of 'fixme' eluded per comment in logfile. -- 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.
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 --- 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. *** -- 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.
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 --- 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 -- 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.
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 --- 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. -- 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.
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 --- 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, -- 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.
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 --- 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 -- 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.
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 --- 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. -- 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.
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 --- 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. -- 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.
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 --- 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. -- 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.
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 --- 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 -- 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.
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 --- 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. -- 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.
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. -- 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.
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.
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 Bob <bob+wine(a)mcelrath.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bob+wine(a)mcelrath.org --- 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. --- Comment #48 from Bob <bob+wine(a)mcelrath.org> 2009-08-04 18:45:42 --- 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. -- 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.
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 Bob <bob+wine(a)mcelrath.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bob+wine(a)mcelrath.org --- 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. --- Comment #48 from Bob <bob+wine(a)mcelrath.org> 2009-08-04 18:45:42 --- 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(a)gmail.com> 2009-08-04 21:28:37 --- 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. -- 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.
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 Bob <bob+wine(a)mcelrath.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bob+wine(a)mcelrath.org --- 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. --- Comment #48 from Bob <bob+wine(a)mcelrath.org> 2009-08-04 18:45:42 --- 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(a)gmail.com> 2009-08-04 21:28:37 --- 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 <taedium_vitae(a)eml.cc> 2009-08-04 21:51:42 --- The witcher no longer crashes, either. -- 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.
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 Bob <bob+wine(a)mcelrath.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bob+wine(a)mcelrath.org --- 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. --- Comment #48 from Bob <bob+wine(a)mcelrath.org> 2009-08-04 18:45:42 --- 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(a)gmail.com> 2009-08-04 21:28:37 --- 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 <taedium_vitae(a)eml.cc> 2009-08-04 21:51:42 --- The witcher no longer crashes, either. --- Comment #51 from Rico <kgbricola(a)web.de> 2009-08-05 15:03:02 --- The patch (commit http://source.winehq.org/git/wine.git/?a=commit; h=c10bdbefd69786846b035d1c38de3052bed67875 ) fixes Gothic3, too. -- 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.
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 Bob <bob+wine(a)mcelrath.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bob+wine(a)mcelrath.org Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- 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. --- Comment #48 from Bob <bob+wine(a)mcelrath.org> 2009-08-04 18:45:42 --- 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(a)gmail.com> 2009-08-04 21:28:37 --- 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 <taedium_vitae(a)eml.cc> 2009-08-04 21:51:42 --- The witcher no longer crashes, either. --- Comment #51 from Rico <kgbricola(a)web.de> 2009-08-05 15:03:02 --- The patch (commit http://source.winehq.org/git/wine.git/?a=commit; h=c10bdbefd69786846b035d1c38de3052bed67875 ) fixes Gothic3, too. --- Comment #52 from Alexandre Julliard <julliard(a)winehq.org> 2009-08-06 10:23:54 --- Marking fixed then. -- 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.
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 Bob <bob+wine(a)mcelrath.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bob+wine(a)mcelrath.org Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED Status|RESOLVED |CLOSED --- 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. --- Comment #48 from Bob <bob+wine(a)mcelrath.org> 2009-08-04 18:45:42 --- 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(a)gmail.com> 2009-08-04 21:28:37 --- 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 <taedium_vitae(a)eml.cc> 2009-08-04 21:51:42 --- The witcher no longer crashes, either. --- Comment #51 from Rico <kgbricola(a)web.de> 2009-08-05 15:03:02 --- The patch (commit http://source.winehq.org/git/wine.git/?a=commit; h=c10bdbefd69786846b035d1c38de3052bed67875 ) fixes Gothic3, too. --- Comment #52 from Alexandre Julliard <julliard(a)winehq.org> 2009-08-06 10:23:54 --- Marking fixed then. --- Comment #53 from Alexandre Julliard <julliard(a)winehq.org> 2009-08-07 12:52:03 --- Closing bugs fixed in 1.1.2,7. -- 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.
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 Bob <bob+wine(a)mcelrath.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bob+wine(a)mcelrath.org Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED Status|RESOLVED |CLOSED --- 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. --- Comment #48 from Bob <bob+wine(a)mcelrath.org> 2009-08-04 18:45:42 --- 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(a)gmail.com> 2009-08-04 21:28:37 --- 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 <taedium_vitae(a)eml.cc> 2009-08-04 21:51:42 --- The witcher no longer crashes, either. --- Comment #51 from Rico <kgbricola(a)web.de> 2009-08-05 15:03:02 --- The patch (commit http://source.winehq.org/git/wine.git/?a=commit; h=c10bdbefd69786846b035d1c38de3052bed67875 ) fixes Gothic3, too. --- Comment #52 from Alexandre Julliard <julliard(a)winehq.org> 2009-08-06 10:23:54 --- Marking fixed then. --- Comment #53 from Alexandre Julliard <julliard(a)winehq.org> 2009-08-07 12:52:03 --- Closing bugs fixed in 1.1.2,7. --- Comment #54 from drachu(a)gmail.com 2009-08-24 17:03:58 --- Created an attachment (id=23241) --> (http://bugs.winehq.org/attachment.cgi?id=23241) dump of crash on version 1.1.28 -- 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.
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 Bob <bob+wine(a)mcelrath.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bob+wine(a)mcelrath.org Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED Status|RESOLVED |CLOSED --- 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. --- Comment #48 from Bob <bob+wine(a)mcelrath.org> 2009-08-04 18:45:42 --- 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(a)gmail.com> 2009-08-04 21:28:37 --- 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 <taedium_vitae(a)eml.cc> 2009-08-04 21:51:42 --- The witcher no longer crashes, either. --- Comment #51 from Rico <kgbricola(a)web.de> 2009-08-05 15:03:02 --- The patch (commit http://source.winehq.org/git/wine.git/?a=commit; h=c10bdbefd69786846b035d1c38de3052bed67875 ) fixes Gothic3, too. --- Comment #52 from Alexandre Julliard <julliard(a)winehq.org> 2009-08-06 10:23:54 --- Marking fixed then. --- Comment #53 from Alexandre Julliard <julliard(a)winehq.org> 2009-08-07 12:52:03 --- Closing bugs fixed in 1.1.2,7. --- Comment #54 from drachu(a)gmail.com 2009-08-24 17:03:58 --- 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(a)gmail.com 2009-08-24 17:05:51 --- Created an attachment (id=23242) --> (http://bugs.winehq.org/attachment.cgi?id=23242) dump of crash on version 1.1.28 -- 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.
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 Bob <bob+wine(a)mcelrath.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bob+wine(a)mcelrath.org Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED Status|RESOLVED |CLOSED drachu(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |drachu(a)gmail.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. --- Comment #48 from Bob <bob+wine(a)mcelrath.org> 2009-08-04 18:45:42 --- 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(a)gmail.com> 2009-08-04 21:28:37 --- 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 <taedium_vitae(a)eml.cc> 2009-08-04 21:51:42 --- The witcher no longer crashes, either. --- Comment #51 from Rico <kgbricola(a)web.de> 2009-08-05 15:03:02 --- The patch (commit http://source.winehq.org/git/wine.git/?a=commit; h=c10bdbefd69786846b035d1c38de3052bed67875 ) fixes Gothic3, too. --- Comment #52 from Alexandre Julliard <julliard(a)winehq.org> 2009-08-06 10:23:54 --- Marking fixed then. --- Comment #53 from Alexandre Julliard <julliard(a)winehq.org> 2009-08-07 12:52:03 --- Closing bugs fixed in 1.1.2,7. --- Comment #54 from drachu(a)gmail.com 2009-08-24 17:03:58 --- 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(a)gmail.com 2009-08-24 17:05:51 --- 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(a)gmail.com 2009-08-24 17:13:25 --- 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. -- 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.
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 Bob <bob+wine(a)mcelrath.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bob+wine(a)mcelrath.org Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED Status|RESOLVED |CLOSED drachu(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |drachu(a)gmail.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. --- Comment #48 from Bob <bob+wine(a)mcelrath.org> 2009-08-04 18:45:42 --- 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(a)gmail.com> 2009-08-04 21:28:37 --- 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 <taedium_vitae(a)eml.cc> 2009-08-04 21:51:42 --- The witcher no longer crashes, either. --- Comment #51 from Rico <kgbricola(a)web.de> 2009-08-05 15:03:02 --- The patch (commit http://source.winehq.org/git/wine.git/?a=commit; h=c10bdbefd69786846b035d1c38de3052bed67875 ) fixes Gothic3, too. --- Comment #52 from Alexandre Julliard <julliard(a)winehq.org> 2009-08-06 10:23:54 --- Marking fixed then. --- Comment #53 from Alexandre Julliard <julliard(a)winehq.org> 2009-08-07 12:52:03 --- Closing bugs fixed in 1.1.2,7. --- Comment #54 from drachu(a)gmail.com 2009-08-24 17:03:58 --- 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(a)gmail.com 2009-08-24 17:05:51 --- 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(a)gmail.com 2009-08-24 17:13:25 --- 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(a)kievinfo.com> 2009-08-24 23:06:50 --- (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. -- 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.
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 Bob <bob+wine(a)mcelrath.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bob+wine(a)mcelrath.org Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED Status|RESOLVED |CLOSED drachu(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |drachu(a)gmail.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. --- Comment #48 from Bob <bob+wine(a)mcelrath.org> 2009-08-04 18:45:42 --- 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(a)gmail.com> 2009-08-04 21:28:37 --- 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 <taedium_vitae(a)eml.cc> 2009-08-04 21:51:42 --- The witcher no longer crashes, either. --- Comment #51 from Rico <kgbricola(a)web.de> 2009-08-05 15:03:02 --- The patch (commit http://source.winehq.org/git/wine.git/?a=commit; h=c10bdbefd69786846b035d1c38de3052bed67875 ) fixes Gothic3, too. --- Comment #52 from Alexandre Julliard <julliard(a)winehq.org> 2009-08-06 10:23:54 --- Marking fixed then. --- Comment #53 from Alexandre Julliard <julliard(a)winehq.org> 2009-08-07 12:52:03 --- Closing bugs fixed in 1.1.2,7. --- Comment #54 from drachu(a)gmail.com 2009-08-24 17:03:58 --- 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(a)gmail.com 2009-08-24 17:05:51 --- 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(a)gmail.com 2009-08-24 17:13:25 --- 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(a)kievinfo.com> 2009-08-24 23:06:50 --- (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(a)gmail.com 2009-08-26 02:07:17 --- 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'. -- 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.
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 Bob <bob+wine(a)mcelrath.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bob+wine(a)mcelrath.org Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED Status|RESOLVED |CLOSED drachu(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |drachu(a)gmail.com Joachim Rousseau <syrion.com(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |syrion.com(a)gmail.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. --- Comment #48 from Bob <bob+wine(a)mcelrath.org> 2009-08-04 18:45:42 --- 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(a)gmail.com> 2009-08-04 21:28:37 --- 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 <taedium_vitae(a)eml.cc> 2009-08-04 21:51:42 --- The witcher no longer crashes, either. --- Comment #51 from Rico <kgbricola(a)web.de> 2009-08-05 15:03:02 --- The patch (commit http://source.winehq.org/git/wine.git/?a=commit; h=c10bdbefd69786846b035d1c38de3052bed67875 ) fixes Gothic3, too. --- Comment #52 from Alexandre Julliard <julliard(a)winehq.org> 2009-08-06 10:23:54 --- Marking fixed then. --- Comment #53 from Alexandre Julliard <julliard(a)winehq.org> 2009-08-07 12:52:03 --- Closing bugs fixed in 1.1.2,7. --- Comment #54 from drachu(a)gmail.com 2009-08-24 17:03:58 --- 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(a)gmail.com 2009-08-24 17:05:51 --- 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(a)gmail.com 2009-08-24 17:13:25 --- 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(a)kievinfo.com> 2009-08-24 23:06:50 --- (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(a)gmail.com 2009-08-26 02:07:17 --- 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(a)gmail.com> 2009-08-26 08:43:44 --- (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. -- 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.
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 Bob <bob+wine(a)mcelrath.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bob+wine(a)mcelrath.org Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED Status|RESOLVED |CLOSED drachu(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |drachu(a)gmail.com Joachim Rousseau <syrion.com(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |syrion.com(a)gmail.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. --- Comment #48 from Bob <bob+wine(a)mcelrath.org> 2009-08-04 18:45:42 --- 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(a)gmail.com> 2009-08-04 21:28:37 --- 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 <taedium_vitae(a)eml.cc> 2009-08-04 21:51:42 --- The witcher no longer crashes, either. --- Comment #51 from Rico <kgbricola(a)web.de> 2009-08-05 15:03:02 --- The patch (commit http://source.winehq.org/git/wine.git/?a=commit; h=c10bdbefd69786846b035d1c38de3052bed67875 ) fixes Gothic3, too. --- Comment #52 from Alexandre Julliard <julliard(a)winehq.org> 2009-08-06 10:23:54 --- Marking fixed then. --- Comment #53 from Alexandre Julliard <julliard(a)winehq.org> 2009-08-07 12:52:03 --- Closing bugs fixed in 1.1.2,7. --- Comment #54 from drachu(a)gmail.com 2009-08-24 17:03:58 --- 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(a)gmail.com 2009-08-24 17:05:51 --- 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(a)gmail.com 2009-08-24 17:13:25 --- 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(a)kievinfo.com> 2009-08-24 23:06:50 --- (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(a)gmail.com 2009-08-26 02:07:17 --- 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(a)gmail.com> 2009-08-26 08:43:44 --- (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(a)gmail.com 2009-08-26 18:16:14 --- 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. -- 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.
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 Bob <bob+wine(a)mcelrath.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bob+wine(a)mcelrath.org Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED Status|RESOLVED |CLOSED drachu(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |drachu(a)gmail.com Joachim Rousseau <syrion.com(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |syrion.com(a)gmail.com --- Comment #36 from Jeff Zaroyko <jeffz(a)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(a)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(a)gmail.com> 2009-07-28 20:47:11 CDT --- This bug also occurs with The Witcher. --- Comment #39 from N3o <diafoirus(a)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(a)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(a)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(a)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(a)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(a)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(a)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(a)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(a)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(a)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(a)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(a)gmail.com> 2009-08-04 21:51:42 CDT --- The witcher no longer crashes, either. --- Comment #51 from Rico <kgbricola(a)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(a)winehq.org> 2009-08-06 10:23:54 CDT --- Marking fixed then. --- Comment #53 from Alexandre Julliard <julliard(a)winehq.org> 2009-08-07 12:52:03 CDT --- Closing bugs fixed in 1.1.2,7. --- Comment #54 from drachu(a)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(a)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(a)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(a)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(a)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(a)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(a)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. -- 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.
participants (1)
-
wine-bugs＠winehq.org