https://bugs.winehq.org/show_bug.cgi?id=50190
Bug ID: 50190 Summary: Shockwave Projector: crash on launch Product: Wine Version: 5.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: parker.l.reed@gmail.com Distribution: ---
Created attachment 68705 --> https://bugs.winehq.org/attachment.cgi?id=68705 Backtrace of crash
Shockwave Projector Crashes on launch on 5.22 and git.
This is a regression as it worked in 5.21 and below.
What happens: crashes on launch with backtrace
Archive with the projector and test file.
Run with
wine start /unix SPR.exe slipstream.dcr
https://bluepload.unstable.life/shockwave.tar.gz
[parker@wolfcola ~/]$ sha1sum shockwave.tar.gz 8bad0e1b26b7c35306aca6eb6da5529e54b0274c shockwave.tar.gz
It will either crash or stop on a grey screen.
(The program and files are part of Flashpoint as a whole. That is their file hosting service with the specific use case)
Tried running with WINEDEBUG=+relay but it seems to not crash with that enabled...
https://bugs.winehq.org/show_bug.cgi?id=50190
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download, regression
--- Comment #1 from Austin English austinenglish@gmail.com --- Please run a regression test: https://wiki.winehq.org/Regression_Testing
https://bugs.winehq.org/show_bug.cgi?id=50190
--- Comment #2 from Parker parker.l.reed@gmail.com --- Well, I took so long getting around to bisect that it ended up getting fixed in the meantime. Tried bisecting with the current rev as good and 5.22 as bad but git complained that I couldn't do that.
The issue is fully resolved now and the program runs as expected.
Close this if need be. I can try to track down the commit if needed.
https://bugs.winehq.org/show_bug.cgi?id=50190
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |z.figura12@gmail.com Resolution|--- |FIXED
--- Comment #3 from Zebediah Figura z.figura12@gmail.com --- It's not really necessary to find the commit that fixed it. Note though that if interested, you can just reverse good/bad (or use the --term-old and --term-new arguments).
That said, it may be worth checking a few times. That WINEDEBUG=+relay fixes the bug often indicates a race condition.
https://bugs.winehq.org/show_bug.cgi?id=50190
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #4 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 6.0-rc2.