[Bug 59673] New: Densha De Go! Professional 2 crashes on launch since commit 6048ac5dfeb
http://bugs.winehq.org/show_bug.cgi?id=59673 Bug ID: 59673 Summary: Densha De Go! Professional 2 crashes on launch since commit 6048ac5dfeb Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs@list.winehq.org Reporter: duuqnd@stacken.kth.se Distribution: --- Created attachment 80764 --> http://bugs.winehq.org/attachment.cgi?id=80764 backtrace Since commit 6048ac5dfeb, found by performing a git bisect, the game Densha De Go! Professional 2 crashes on startup due to a NULL pointer dereference. I've attached a backtrace, though in previous commits it used to crash in a different function. The backtrace was made from a build compiled from the master branch as of 2026-04-18 (which happens to be tagged wine-11.7). As mentioned, the culprit is as far as I can tell the change introduced in commit 6048ac5dfeb, but I'll admit that I don't know why those changes were made nor why they cause the problem. They absolutely seem related though. It doesn't seem like it should be difficult to figure out for those who are familiar with that part of the code, but I could be wrong on that. -- 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=59673 Austin English <austinenglish@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |6048ac5dfebd7090672ec1c26e6 | |e15dfd51d5a8d Keywords| |regression Summary|Densha De Go! Professional |Densha De Go! Professional |2 crashes on launch since |2 crashes on launch |commit 6048ac5dfeb | -- 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=59673 Austin English <austinenglish@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|unspecified |11.0 -- 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=59673 Rémi Bernon <rbernon@codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rbernon@codeweavers.com --- Comment #1 from Rémi Bernon <rbernon@codeweavers.com> --- I can't reproduce with current git HEAD on Mesa / Intel and the game works fine for me. Could you attach a log file with WINEDEBUG=+loaddll,+pid,+x11drv,+d3d,+opengl,+wgl,+win ? -- 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=59673 --- Comment #2 from duuqnd@stacken.kth.se --- I'm rebuilding a Wine from the current latest commit now. That will take a while so I'll comment with the log asked for once that's done. In the mean time I can mention that I'm also using Mesa, but with AMD card (a Radeon RX 9060 XT on my desktop computer, some integrated whatever AMD on my laptop, same error on both). The error the game gave me first (when I was on the release Fedora shipped at the time) was that initializing the graphics class failed, but the Direct3D call the message box described was said to have succeeded with an S_OK. It was quite literally a "failed: call succeeded" kind of situation. For a while I tried decompiling some parts of the game to figure out how that could happen, but had no luck. While performing the git bisect it ended up telling me different things at different points. I think I remember seeing some of those calls actually being said to have failed. And for some commits I instead got hard crashes inside the wined3d code. I'll attach some screenshots. -- 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=59673 --- Comment #3 from duuqnd@stacken.kth.se --- Created attachment 80953 --> http://bugs.winehq.org/attachment.cgi?id=80953 screenshot 1, a slightly different backtrace -- 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=59673 --- Comment #4 from duuqnd@stacken.kth.se --- Created attachment 80954 --> http://bugs.winehq.org/attachment.cgi?id=80954 screenshot 2, the first in-game error message -- 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=59673 --- Comment #5 from duuqnd@stacken.kth.se --- Created attachment 80955 --> http://bugs.winehq.org/attachment.cgi?id=80955 screenshot 3, a later in-game error message -- 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=59673 --- Comment #6 from duuqnd@stacken.kth.se --- Created attachment 80956 --> http://bugs.winehq.org/attachment.cgi?id=80956 Debug log from using latest Wine version (0c0d2643) Produced using WINEDEBUG=+loaddll,+pid,+x11drv,+d3d,+opengl,+wgl,+win. The game hard crashes on launch, backtrace seems nearly identical to the first one. I'm not sure what to look for in the debug log here but it looks like it's failing to make a GL context at a few points? -- 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=59673 --- Comment #7 from Rémi Bernon <rbernon@codeweavers.com> --- Thank you! I think this might be caused by some interaction of the blamed commit and wined3d multithreaded command stream that is apparently disabled in your prefix. This is a bug and it should probably work but I'm not sure how to fix it properly yet. You might want to edit the user.reg file in the game prefix, to remove the csmt key (or set it to 1) under Software\\Wine\\AppDefaults\\dgopro2.exe\\Direct3D, and see if it helps. -- 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=59673 --- Comment #8 from duuqnd@stacken.kth.se --- I tried adding that registry key and it does seem to mitigate the issue. -- 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=59673 mata <sutupud@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sutupud@yahoo.com --- Comment #9 from mata <sutupud@yahoo.com> --- One observation related to this, the way this is presented in winecfg if this key is unset (or set to 1) is: [✔️] Enable CSMT for better graphic performance (deprecated) To me, it's not really immediately clear what exactly is deprecated I can easily see how it would lead someone to think "hmmm, this deprecated setting is enabled, probably bettter disable it". It would be better if it would make it clear that *disabling* it is deprecated. -- 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=59673 --- Comment #10 from duuqnd@stacken.kth.se --- For what it's worth, I have no memory of tinkering with winecfg settings since creating this prefix. I may be wrong though, so I'll test with a fresh prefix in a bit. -- 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=59673 --- Comment #11 from mata <sutupud@yahoo.com> --- (In reply to duuqnd from comment #10)
For what it's worth, I have no memory of tinkering with winecfg settings since creating this prefix. I may be wrong though, so I'll test with a fresh prefix in a bit.
It applies only to staging anyway, and to the global HKCUS\oftware\Wine\Direct3D key... So if that doesn't apply, something else must have written it, not sure what. -- 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)
-
WineHQ Bugzilla