WMA breaks WACUP 1.99.52.24626 (x64)

[freestone]

First post here. Hopefully it's in the correct area and not a known issue.

No matter how I try to get x64 build #24626 to play a .WMA file, drop/drop, File/Open, it dies. Yesterday it closed instantly, today it takes its time, but eventually closes. In any case, Event Viewer Application Log shows:

Faulting application name: wacup.exe, version: 1.99.52.24626, time stamp: 0x6a50de0d
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000409
Fault offset: 0x00007ffae06d528f
Faulting process id: 0xDD8
Faulting application start time: 0x1DD14765D73AA21
Faulting application path: V:\My Program Files\WACUP\WACUP 1.99.52.24626 (x64)\wacup.exe
Faulting module path: unknown
Report Id: dc920a57-c46f-4fc8-acfc-457c6fc3bea0
Faulting package full name:
Faulting package-relative application ID:

WACUP 1.99.52.24626 (x86) plays .WMA files with no problem as does earlier version WACUP 1.99.50.24496 (x64).

Let me know what additional information you may want. Thank you for the program!

[dro]

It's not something I've tried in an age so it regressing isn't too surprising with some of the other changes that have been made to avoid other crashes affecting the recent builds. Though I've just re-checked a few example files & those played ok in the build.

You'll need to run it via the crash report collector mode (it'll be a shortcut in the start menu or by manually running wacup.exe /procdump or by going to preferences -> advanced -> error reporting & following the steps at the bottom of the prefs page) to try to generate a process dmp file when trying to replicate the issue in that mode (the event viewer log doesn't give me anything I can actually work with to debug the issue).

Once it's crashed, you'll then need to run wacup so its crash reporter can collect & submit the files - reply back to say it's been done so I can then hopefully match up the crash report from that time (I'll check back on this thread tomorrow as my time's up for today). I also don't see anything obvious from the summary log I get of the few x64 crash reports I've not looked at from today which leaves me to assume wacup's crash reporter isn't able to be triggered by the issue which prevents it from auto-submitting anything to the server (unless internet access for the program is being blocked). It might also be helpful to pm me a copy of a small file that's failing for you so I can also check that out in case it's something to do with the metadata handling for it.

[freestone]

It's been done. I've PMed with a sample file and its crash report file (report_20260715211521.zip) attached.

[dro]

The problem is within the in_what (directshow decoder) plug-in but is possibly tied to a change in the core so it'll need a new build instead of just a post-release update from what I can see at the moment. It keeps crashing for you on loading with the file(s) in the main playlist as it's trying to generate a waveform seeker preview when started which is then hitting the problem with how the internal player is being destroyed. It's not necessarily a new issue as I saw some of this when I was making the plug-in but the x64 build is more prone to it afaict.

[freestone]

Thank you for your time to look into the problem and your in-depth explanation. The issue is easily worked around and you are aware of the issue (again).