 |
You are the first person to report this issue after the 1.22 release, in which it was supposedly fixed. Are you sure you are running OpenMPT 1.22.02? If yes, which output driver are you using in OpenMPT? DirectSound? |
|
|
Also, please provide the crash dump that OpenMPT should have created during the crash. |
 |
where is the crash dumps??? |
|
|
If it really crashed, it should have said something like "OpenMPT crashed and needs to be closed." with the location of the dump. It's in %TEMP%\OpenMPT Crash Files. |
 |
I have seen that behavior for a long time and if it is fixed indeed, that is excellent. It is quite annoying. |
|
|
There was a total of three identical bug reports regarding exactly this issue, and after supposedly fixing this DirectSound issue (it shouldn't happen with any of the other drivers in OpenMPT), I only got positive replies for 1.22 that the issue was fixed. So I cannot believe that the issue now magically returned for a single person. |
 |
I have the issue as well. I should note that I'm using a Realtek sound card/driver, and I have never had the bug on computers with an audio driver other than realtek. Also, for me it's not even necessarily after leaving it open, it's also commonly after playing audio in another application. |
|
|
Can you please provide one of the crash dumps generated by OpenMPT then? |
|
|
It does not create a crash dump. It simply hangs and then the default Windows crash dialog pops up and takes over trying to kill the application. Modplug's death in this scenario can range from 10 seconds with no harm done to crashing my computer. |
|
|
Then please let Windows generate a dump for you as explained in this post (don't miss the 64-Bit part!): |
|
|
Soo... crash dumps? |
 |
So... 7 months later, still no crashdumps. Does this still happen, or can this be disregarded? I mean, there's no way our devs can fix it without proper info. |
- Anonymous
