 |
Well, there's nothing we can do without that crash report, so please use one of the plenty file hosts out there on the internet (dropbox/google drive/whatever is also fine). Just to rule out one of the most frequent candidates for random crashes, are you using a DirectSound device (yellow X icon) in the soundcard settings? |
|
|
I'll have to close this report if you don't provide a crash dump or any other kind of useful information. For a start, OpenMPT's automatically created stack dump is only a few hundred KB in size and may already be helpful. |
 |
Let me upload them to Google Drive, then. It might take a while, though. But yes, I was using DirectSound, since WASAPI kept getting random performance drops (including horrible stutering on the sound quality). The WASAPI thing seems to have already been fixed, though, so I switched back. UPDATE: Here is the Drive link: https://drive.google.com/file/d/0B1URcZnhifwbX1g2Z3RrVmk5UXc/view?usp=sharing |
|
|
The dump files are not really debugable, since there was a crash somewhere in the sound device code which triggered an infinite loop of further crashes. PS1: It really wasn't necessary to include all crash dumps (they have a timestamp for a reason), let alone all the hundreds of MBs of trace logs and the recovered module files. PS2: Next time you report a bug and use the stable version, then please state the correct version in the bug information (OpenMPT 1.24.02.00 vs OpenMPT 1.24.02.*), as this just adds a lot of confusion when debugging. |
|
|
Sorry for that, I'll keep in mind next time. The reason I selected the testing version was because I thought I was running on a test build at the time >.< As for attaching multiple dumps, I couldn't remember which one was which, and I figured it was better to give you more information than to give you less. |
|
|
Since WASAPI is working fine for you, I'll put this report on hold and link it to the other problematic DSound reports. |
- Anonymous
