http://bugs.winehq.org/show_bug.cgi?id=20467
Summary: Battle Realms: Crashes on closing Product: Wine Version: 1.1.28 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: debian@carbon-project.org
Created an attachment (id=24351) --> (http://bugs.winehq.org/attachment.cgi?id=24351) Backtrace of the crash on closing.
When closing Battle Realms (pressing the »Leave« button in the game), the application crashes. I've attached a backtrace from such a crash (the attached backtrace was generated by Wine 1.1.32 but the problem exists at least since 1.1.28, see http://appdb.winehq.org/objectManager.php?sClass=version&iId=4394&iTestingId=44308).
If you should need more information, please feel free to ask me for it.
http://bugs.winehq.org/show_bug.cgi?id=20467
Cùran debian@carbon-project.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #24351|application/octet-stream |text/plain mime type| |
http://bugs.winehq.org/show_bug.cgi?id=20467
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |minor
--- Comment #1 from Vitaliy Margolen vitaliy@kievinfo.com 2009-10-25 14:19:08 --- If this a regression, please perform regression testing to find the patch that caused the problem. http://wiki.winehq.org/RegressionTesting
http://bugs.winehq.org/show_bug.cgi?id=20467
--- Comment #2 from Cùran debian@carbon-project.org 2009-10-25 14:24:21 --- (In reply to comment #1)
Can't say whether it is a regression or not. I installed Battle Realms for the first time with 1.1.28, it's a long time since I last played it. Therefore I wouldn't know a »good revision«.
http://bugs.winehq.org/show_bug.cgi?id=20467
Alexander Nicolaysen Sørnes alex@thehandofagony.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |alex@thehandofagony.com Component|-unknown |directx-d3d
--- Comment #3 from Alexander Nicolaysen Sørnes alex@thehandofagony.com 2009-10-26 11:15:10 --- Looks like a bug in WineD3D
http://bugs.winehq.org/show_bug.cgi?id=20467
--- Comment #4 from Cùran debian@carbon-project.org 2010-01-29 07:01:09 --- Confirming with 1.1.37
http://bugs.winehq.org/show_bug.cgi?id=20467
--- Comment #5 from Cùran debian@carbon-project.org 2010-02-10 10:06:30 --- Confirming with 1.1.38.
http://bugs.winehq.org/show_bug.cgi?id=20467
--- Comment #6 from Cùran debian@carbon-project.org 2010-02-20 12:51:01 --- Confirming with 1.1.39.
http://bugs.winehq.org/show_bug.cgi?id=20467
Cùran debian@carbon-project.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #24351|0 |1 is obsolete| |
--- Comment #7 from Cùran debian@carbon-project.org 2010-03-07 08:54:55 --- Created an attachment (id=26667) --> (http://bugs.winehq.org/attachment.cgi?id=26667) Backtrace of the crash on closing (WINEDEBUG with d3d channels;1.1.40).
This is more or less the same as the backtrace in attachment 24351, but with all d3d debugging channels activated (I activated them because in bug 21515, comment 116 it is said, that one needs generally almost all d3d debugging channels to debug a d3d issue and in comment #3 it was speculated, that this might be WineD3D related). If you want/need other channels, just let me know.
Apart from that, I can reproduce the crash with 1.1.40.
http://bugs.winehq.org/show_bug.cgi?id=20467
--- Comment #8 from Cùran debian@carbon-project.org 2010-05-13 15:03:31 --- After some silence (due to time constraints) I like to come back and reconfirm the existence of this bug with 1.1.44.
http://bugs.winehq.org/show_bug.cgi?id=20467
Cùran debian@carbon-project.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #26667|0 |1 is obsolete| |
--- Comment #9 from Cùran debian@carbon-project.org 2010-07-07 07:50:48 --- Created an attachment (id=29421) --> (http://bugs.winehq.org/attachment.cgi?id=29421) Backtrace of the crash on closing (WINEDEBUG with d3d channels;1.2 RC6)
I've attached a new backtrace with 1.2 RC6 (LZMA-compressed) and like to confirm the existence of this bug with 1.2 RC6.
http://bugs.winehq.org/show_bug.cgi?id=20467
Cùran debian@carbon-project.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #29421|0 |1 is obsolete| |
--- Comment #10 from Cùran debian@carbon-project.org 2010-07-31 14:49:19 --- Created an attachment (id=29952) --> (http://bugs.winehq.org/attachment.cgi?id=29952) Backtrace of the crash on closing (WINEDEBUG with d3d channels;1.3.0)
Confirming the bug with 1.3.0.
The attached backtrace (XZ compressed) was created by Wine 1.3.0 and doesn't seem to differ much, but I let the judgement to people with more knowledge about the internals of Wine. Debugging channels used: +d3d,+d3d8,+d3d9,+d3d10,+d3d10core,+d3d_caps,+d3d_constants,+d3d_decl,+d3d_draw,+d3drm,+d3d_shader,+d3d_surface,+d3d_texture,+d3dx,+d3dxof,+d3dxof_parsing,+fps,+gl_compat
http://bugs.winehq.org/show_bug.cgi?id=20467
Cùran debian@carbon-project.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #29952|0 |1 is obsolete| |
--- Comment #11 from Cùran debian@carbon-project.org 2011-03-19 11:44:24 CDT --- Created an attachment (id=33717) --> (http://bugs.winehq.org/attachment.cgi?id=33717) Crash with Wine 1.3.16
Still there with 1.3.16
http://bugs.winehq.org/show_bug.cgi?id=20467
--- Comment #12 from Henri Verbeet hverbeet@gmail.com 2011-03-23 07:02:39 CDT --- Created an attachment (id=33781) --> (http://bugs.winehq.org/attachment.cgi?id=33781) patch
Does the attached patch make it any better? Unfortunately I'm unable to reproduce this with the demo, so this is completely untested.
http://bugs.winehq.org/show_bug.cgi?id=20467
Cùran debian@carbon-project.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #33717|0 |1 is obsolete| |
--- Comment #13 from Cùran debian@carbon-project.org 2011-03-23 12:14:50 CDT --- Created an attachment (id=33784) --> (http://bugs.winehq.org/attachment.cgi?id=33784) Crash with Wine 1.3.16 and the patch proposed in comment #12
(In reply to comment #12)
Does the attached patch make it any better?
No, it doesn't. Basically the same output except for the different memory addresses, that the crash now occurs in a read access where the previous had the unhandled exception in a write access and that the function in which it happens is now "IDirect3DDeviceImpl_7_Release" (instead of "IWineD3DDeviceImpl_SetIndexBuffer"). Everything else matches line for line AFAICS. Sill attached a new version of the log for you to check.
http://bugs.winehq.org/show_bug.cgi?id=20467
--- Comment #14 from Henri Verbeet hverbeet@gmail.com 2011-03-23 12:29:50 CDT --- (In reply to comment #13)
No, it doesn't. Basically the same output except for the different memory addresses, that the crash now occurs in a read access where the previous had the unhandled exception in a write access and that the function in which it happens is now "IDirect3DDeviceImpl_7_Release" (instead of "IWineD3DDeviceImpl_SetIndexBuffer"). Everything else matches line for line AFAICS. Sill attached a new version of the log for you to check.
I think that's (minor) progress, actually. The crash seems to suggest "d3d_target" is NULL at that point. Could you create a +ddraw,+d3d,+d3d_surface log and attach it here?
http://bugs.winehq.org/show_bug.cgi?id=20467
Cùran debian@carbon-project.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #33784|0 |1 is obsolete| |
--- Comment #15 from Cùran debian@carbon-project.org 2011-03-24 05:23:46 CDT --- Created an attachment (id=33794) --> (http://bugs.winehq.org/attachment.cgi?id=33794) Crash with Wine 1.3.16 and the patch proposed in comment #12 with req. debugging channels
I killed the process when it had reached 23GB and wasn't showing any inclination to come to an end. Thus I've just attached the firs 240001 lines, the last 247 lines show what was coming afterwards (so far). Just decrease the counter by one.
Let me know if you need further information.
http://bugs.winehq.org/show_bug.cgi?id=20467
--- Comment #16 from Henri Verbeet hverbeet@gmail.com 2011-03-27 10:25:05 CDT --- (In reply to comment #15)
trace:ddraw:ddraw_surface7_QueryInterface (0x131d70) returning IDirectDrawGammaControl interface at 0x131d78
...
trace:ddraw:ddraw_gamma_control_Release iface 0x131d78. trace:ddraw:ddraw_surface7_Release 0x131d70 decreasing refcount to 2. trace:ddraw:ddraw_gamma_control_Release iface 0x131d78. trace:ddraw:ddraw_surface7_Release 0x131d70 decreasing refcount to 1. trace:ddraw:ddraw_gamma_control_Release iface 0x131d78. trace:ddraw:ddraw_surface7_Release 0x131d70 decreasing refcount to 0. trace:ddraw:ddraw_surface7_Release (0x131d70) Destroying the render target, uninitializing D3D
Looks like this is essentially due to ddraw needing separate ref counts for each surface interface.
http://bugs.winehq.org/show_bug.cgi?id=20467
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #17 from joaopa jeremielapuree@yahoo.fr 2011-06-17 13:28:38 CDT --- Some progress were made in this area. Is it still a bug in current wine?
http://bugs.winehq.org/show_bug.cgi?id=20467
Cùran debian@carbon-project.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #33794|0 |1 is obsolete| |
--- Comment #18 from Cùran debian@carbon-project.org 2011-06-18 12:46:31 CDT --- Created an attachment (id=35193) --> (http://bugs.winehq.org/attachment.cgi?id=35193) Crash with Wine 1.3.22 and req. debugging channels
Sadly this one is still there as you can see from the attached back trace (I've added a new one since you said lots of things have change, maybe the source of the bug becomes clearer from this log).
http://bugs.winehq.org/show_bug.cgi?id=20467
--- Comment #19 from Henri Verbeet hverbeet@gmail.com 2011-07-03 02:07:11 CDT --- (In reply to comment #18)
Sadly this one is still there as you can see from the attached back trace (I've added a new one since you said lots of things have change, maybe the source of the bug becomes clearer from this log).
I'm afraid comment 17 was a bit bit on the optimistic side. Actual refcount separation was done until commit e5d69ba9237de0d461c5896d4377606c23700c9d (notice the date on that). Could you give this a try with current git, and create a new log if the crash still happens?
http://bugs.winehq.org/show_bug.cgi?id=20467
Cùran debian@carbon-project.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #35193|0 |1 is obsolete| |
--- Comment #20 from Cùran debian@carbon-project.org 2011-07-03 08:02:12 CDT --- Created an attachment (id=35413) --> (http://bugs.winehq.org/attachment.cgi?id=35413) No crash with Wine 1.3.23+git38c13e56
As you can see from the attached log (again with all the debugging channels), the crash is gone (I built a snapshot of Git 38c13e56), just some FIXMEs remain. Thus this bug should be fixed with 1.3.24.
http://bugs.winehq.org/show_bug.cgi?id=20467
Cùran debian@carbon-project.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #21 from Cùran debian@carbon-project.org 2011-07-03 10:54:57 CDT --- See comment #20 for details, forgot to set this to RESOLVED FIXED before (should be marked as CLOSED FIXED with 1.3.24).
http://bugs.winehq.org/show_bug.cgi?id=20467
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #22 from Alexandre Julliard julliard@winehq.org 2011-07-08 13:48:06 CDT --- Closing bugs fixed in 1.3.24.