[Bug 29645] New: PCSX2: Software renderer crashes on initialisation when using more than 1 thread
http://bugs.winehq.org/show_bug.cgi?id=29645 Bug #: 29645 Summary: PCSX2: Software renderer crashes on initialisation when using more than 1 thread Product: Wine Version: 1.3.37 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: billy65bob(a)gmail.com Classification: Unclassified I'm not quite sure where, but if the software renderer is instructed to use more than 1 thread, the emulator crashes whenever the GS plugin is being initialised. The crashing message in question is as follows wine: Unhandled page fault on read access to 0x00000000 at address (nil) (thread 0030), starting debugger... No further information is dumped. It works correctly under Windows, but only under wine when a single thread is used. As such I suspect it may be an issue with how threads are handled in wine - but that is simply an uneducated guess. The sourcecode for the application can be found on googlecode. If I can help debug it in some way, let me know. -- 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=29645 DL <dredgingthelake(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dredgingthelake(a)gmail.com --- Comment #1 from DL <dredgingthelake(a)gmail.com> 2012-03-17 22:51:44 CDT --- Works for me with r5127 and wine-1.4. -- 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=29645 --- Comment #2 from Kevin Meyer <billy65bob(a)gmail.com> 2012-03-18 02:36:48 CDT --- IT appears the issue existed under older variations of windows as well, and this was corrected in revision 5089 and 5090. http://code.google.com/p/pcsx2/source/detail?r=5089 But considering the issue didn't show itself on Windows 7 (and Vista by the sounds of it) during these "faulty revisions", I'd prefer to keep it open for now until someone with more experience has had a look at it. -- 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=29645 Jerome Leclanche <adys.wh(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |source Status|UNCONFIRMED |NEW CC| |adys.wh(a)gmail.com Ever Confirmed|0 |1 --- Comment #3 from Jerome Leclanche <adys.wh(a)gmail.com> 2012-03-25 11:45:01 CDT --- 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.
https://bugs.winehq.org/show_bug.cgi?id=29645 --- Comment #4 from Austin English <austinenglish(a)gmail.com> --- This is your friendly reminder that there has been no bug activity for 2 years. Is this still an issue in current (1.7.16 or newer) wine? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=29645 --- Comment #5 from Kevin Meyer <billy65bob(a)gmail.com> --- I just grabbed an old 5088 build of pcsx2 (before the fix) and ran a few games with wine-git revision f820d9723b2725d0fa8cc2012ed50a6869fdb951. The issue I described is no longer occurring; This can probably be marked fixed, but I'm not sure how or where the fix happened. On the other hand, the state of the dx9 hardware renderer appears to have visibly regressed, as though a bad scissor rectangle has been set; I'll file a bug for that once I've had a chance to have a closer look and gather some more info. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=29645 Jerome Leclanche <adys.wh(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Jerome Leclanche <adys.wh(a)gmail.com> ---
I'll file a bug for that
Please do! -- 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.
https://bugs.winehq.org/show_bug.cgi?id=29645 --- Comment #7 from Kevin Meyer <billy65bob(a)gmail.com> --- Scratch that last bit. The OffscreenRendererMode variable was set to backbuffer to workaround bug 35731, that caused the scissoring issue; The crash doesn't occur there either anymore. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=29645 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #8 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 1.7.17. -- 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