GURU MEDITATION: Unhandeled Exception Handler Invoked, application will exit!

[Meguido]

Hello, I'm getting the error window pop-up with the text mentioned in the Title, right after executing the app and so it closes right after that. I tried with the latest version and some others with the same result. Tried with the installer .exe version and the .zip portable one and always the same result.

What's causing this error? I mean, there's no other info about it and the text it's pretty ambiguous.

Regards.

[lordmulder]

Well, it means that the application has "crashed" because of an unhandled exception error 😞

It's hard to guess what might be the problem without additional information 🤔

1. First things first, what operating system and CPU are you running on?
2. Does running LameXP with parameter --console reveal any additional hints on the error?
3. Do you have any so-called "anti-virus" software (other than the standard Windows Defender) installed? If so, try uninstalling it completely, reboot, then check if it makes any difference – just to be sure.
4. Is this a "new" problem/regression with version 4.21? For example, does version 4.20 work okay for your? Try to figure out what was the last "working" version...
5. Finally, please try running the Debug build of LameXP inside of the Windows Debugger!

[Meguido]

Ok, additional info incoming

1. I'm using Windows 10 x64 (v. 21H2) and my CPU is AMD Ryzen 9 7950X
2. Running it with the param --console throws some warnings (don't know if related or not)

Failed to resolve function: ntdll::wine_get_version SetConsoleIcon() has failed! [Error: 0x00004001] NeroAAC encoder binaries not found -> Encoding support will be disabled! QAAC encoder binaries not found -> Encoding support will be disabled! FhgAacEnc encoder binaries not found -> Encoding support will be disabled! FdkAacEnc encoder binaries not found -> Encoding support will be disabled! QAACx64 encoder binaries not found -> Encoding support will be disabled!

3. I have ESET Endpoint as anti-virus. I tried uninstalling it, rebooting and executing this again with no new result
4. I tried from 4.14 up to the lates release, all with the same error
5. It started loading a lot of stuff to just sit there in a white screen like a frozen window and it's doing nothing since then. Found this on the command window in Windows Debugger:

   (4528.2688): Access violation - code c0000005 (first chance)
   First chance exceptions are reported before any exception handling.
   This exception may be expected and handled.
   eax=080734bc ebx=00000000 ecx=06c81964 edx=080734bc esi=06c81960 edi=0000000c
   eip=7446408f esp=0780fb98 ebp=0780fc10 iopl=0         nv up ei ng nz na pe nc
   cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
   WINMM!soundInitWavHdr+0x20:
   7446408f 813852494646    cmp     dword ptr [eax],46464952h ds:002b:080734bc=????????

[lordmulder]

Running it with the param --console throws some warnings (don't know if related or not)

…
QAACx64 encoder binaries not found -> Encoding support will be disabled!

Is that really the last output line before the crash?

---

I tried from 4.14 up to the lates release, all with the same error

That is really weird. It means that it's certainly not a new issue (or regression) in the latest release.

On the other hand, I have not seen this problem on any of my machines, nor has anybody reported a similar issue 🤔

So this would indicate some sort of "anomaly" on your specific system...

---

Found this on the command window in Windows Debugger:

(4528.2688): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=080734bc ebx=00000000 ecx=06c81964 edx=080734bc esi=06c81960 edi=0000000c
eip=7446408f esp=0780fb98 ebp=0780fc10 iopl=0         nv up ei ng nz na pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
WINMM!soundInitWavHdr+0x20:
7446408f 813852494646    cmp     dword ptr [eax],46464952h ds:002b:080734bc=????????

"Access violation" is a rather generic error. It simply means that the program, in one way or another, tried to access a "bad" (e.g. invalid or inaccessible) memory address. There's like a multitude of ways how this might happen...

Anyway, WINMM!soundInitWavHdr gives some hint that is may actually be related to sound output 🤓

Can you please try to edit your LameXP config.ini like this and see if it makes any kind of difference:

[LameXP.2188]
…
Flags\EnableSounds=false

Change the line Flags\EnableSounds to false, or, if it doesn't already exist, append the line to the config file.

For the non-portable version of LameXP, the config file is found at:

C:\Users\YOUR_NAME_HERE\AppData\Local\LoRd_MuldeR\LameXP - Audio Encoder Front-End\config.ini

[Meguido]

Hey, looks like it's working now. Adding this:

[LameXP.2188]
…
Flags\EnableSounds=false

to the config.ini file seem to do the trick. It's now working with no problem!

Thank you so much for your help 😊

I don't know if I should close it as fixed or if you'll need more info, now that's fixed. Let me know, please.

[lordmulder]

Well, it's not really "fixed", we just found a workaround – disable all sound effects.

I have no idea why playing sounds causes a crash on your system. LameXP just uses standard the PlaySound() system function to play sounds. And you are the first one to report any issues with that. So I'm going to assume there is some sort of "problem" with your system, such as a broken sound driver or whatever. Probably not possible to fix on my side.

I'm going to close this, as I believe that there is nothing I can do to improve the situation... :flushed: