Application Error – “External exception E0000008” (player.js line 966) during unexpected track change

[janko74]

Hi everyone,

I’ve been experiencing frequent crashes in MediaMonkey 2024 and I’m trying to narrow down the cause before submitting an official bug report. Maybe someone here has already encountered this issue or found a workaround.

The crash happens suddenly during playback, mostly while multitasking (e.g., when a game is running and MM is playing in the background). The current track stops abruptly, the next one starts, and then MediaMonkey crashes within a few seconds. The error dialog shows the following message:

"Application Error:
App threw an exception “External exception E0000008”
at time Update (file:///controls/player:966:28)
at file:///controls/control:316:17
at file:///mminit.js:852:13)
at line 966!"

The relevant line in player.js is:
if (player.trackPositionMS > this.startTime)

According to an analysis by ChatGPT, the crash may occur right after the current track unexpectedly stops and the next track starts. This suggests a potential race/timing issue in the player control, where player.trackPositionMS could be accessed on a track object that is being released or reinitialized. I've no idea if this is helpful, please feel free to ignore this.

For now, I’ve just installed the Debug Version 2024.2.0.3167 to generate proper log files and hopefully capture the exact conditions that cause the crash. I’m posting this here first to see if anyone else has run into the same problem or has advice on how to fix it before I file a formal report. I will follow bug report instructions from https://www.mediamonkey.com/forum/viewtopic.php?t=86643

System info:

MediaMonkey 2024.1.0.3113 (which was crashing) → updated to 2024.2.0.3167 Debug (Monitoring now with this Version)
NVIDIA GeForce 5070 (updated to Game Ready Driver 581.42)
Windows11 Pro, Intel i7-14700KF, MAG Z790 Tomahawk
Several Audio-Devices installed, mainly using: RodeCaster Pro II
HardDrives: 1TB NVME System-Drive, 2TB NvMe Programs-Drive, 3TB SSD-Sata Data-Drive

A screenshot of the error dialog is attached.


Thanks in advance for any pointers or insights!
Greetings Sascha

[Lowlander]

I'd suggest trying MediaMonkey 2024.2 beta to see if this is already resolved.

Are you using Start Time on the file MediaMonkey crashes?

[janko74]

I'd suggest trying MediaMonkey 2024.2 beta to see if this is already resolved.

Good tip, I will try this next. Last time i tried to analyse similar crashes on my old system, the crashes disappeard after using debug version...

Are you using Start Time on the file MediaMonkey crashes?

No, i'm not using Start Time on any files.

[janko74]

Update: Crash while playback was stopped (still under MM 2024.2.0.3167 Debug Version)

Even with playback stopped, MediaMonkey crashed again. The DebugView log captured the following sequence before the application terminated:

Renderer process crashed!
InstanceManager - window destroyed
Going to kill: MediaMonkeyEngine.exe
Kill leftovers finished, res = 3

According to an analysis by ChatGPT, this indicates that the Chromium-based renderer process (the UI engine of MediaMonkey) crashed unexpectedly, while the playback engine (MediaMonkeyEngine.exe) was later terminated as a result.

The log also shows repeated filesystem errors such as:

ERROR:filesystem_win.cc(128)] GetFileAttributes D:\Steam\dumps\attachments\...

These seem to originate from other Chromium-based apps (like Steam or Epic Games Launcher) and might point to a GPU or overlay conflict — for example with Steam Overlay, Epic Overlay or NVIDIA’s In-Game Overlay.

ChatGPT’s assessment is that this could be a GPU/renderer-level issue, not directly related to the audio engine or specific tracks. Possible contributing factors might include:

GPU hardware acceleration in MediaMonkey’s UI (Chromium renderer)

As a test, ChatGPT suggested temporarily disabling hardware acceleration in Tools → Options → General → Performance and uncheck “Use hardware acceleration when available” (requires restart).

I've updated to 2024.2.0.3168 Debug Version. When it's crashing again, i'll deactivate hardware acceleration and next the overlays.

[Lowlander]

If it still happens on 3168, please capture a full debug log (step 4b) and attach the log to a Support Ticket: https://www.mediamonkey.com/forum/viewtopic.php?t=86643

[janko74]

Today I have sent two DebugView reports (“Renderer process crashed” and “Thread Creation Error”) to Support Ticket.
Unfortunately, MediaMonkey is crashing more and more frequently.

I just experienced several crashes, and this time Windows displayed a “Thread Creation Error” message before MediaMonkey froze completely. I had to kill the process manually via Task Manager. The “Thread Creation Error” seems to be a secondary symptom that occurs when the Chromium-based UI renderer crashes.

It’s extremely annoying, and MediaMonkey is becoming nearly unusable for me at this point. My system was freshly built in July, so this shouldn’t be related to a corrupted or unstable setup.

Man, I really love the Monkey, but this situation is a mess.

[Peke]

Hi,
Interesting, Few questions and possible relations, do you have nVidia GPU and possibly enabled tempered with nVidia App features especially overlays and GPU hardware acceleration?

Also Do you have MB integrated RealTek Sound card? If yes what version of sound card driver you have, Personally one of most stable driver versions I have found is 9239.1

[janko74]

Yes, I'm using Nvidia Geforce RTX 5070. I deactivated hardware acceleration in MM Options. Hardware accelaration GPU-planning, in Windows advanced graphic settings, is on. So maybe GPU Settings override MM settings? NVidia Overlay is active.

Realtek audio is there in device manager. I will deactivate it, and the Nvidia Audio devices too, cause i'm using Rodecaster Pro II as audio device.

[janko74]

Maybe I'm on the trail of the culprit. While scanning the DebugView log, I noticed something:

[34960] UPnP: Renderer name: RX-V671, Renderer UUID: 9ab0c000-f668-11de-9976-00a0de88f04e [34960] MM5 [28168](R) TRemotePlayers._addStoredPlayers [34960] MM5 [28168](R) TRemotePlayers: stored player candidate: {"udn":"9ab0c000-f668-11de-9976-00a0de88f04e","name":"RX-V671","last_seen":"2025-10-13 10:15:52","volume":1,"ip":"http://192.168.178.74:49154/MediaRender ... col":"dlna"} [34960] MM5 [28168](R) TRemotePlayers: stored player candidate: {"udn":"F00DBABE-SA5E-BABA-DADA188ED5A60E84","name":"Philips TV","last_seen":"2025-10-11 20:17:54","volume":1,"ip":"http://192.168.178.24:49153/","isGroup" ... col":"dlna"} [34960] MM5 [28168](R) **********Performance warning: Class TSharedList<UpNp.IRemotePlayer> doesn't implement its own createInstance.

According to ChatGPT’s analysis, this UPnP activity could be related to the renderer crashes.
The old Yamaha RX-V671 and Philips TV are still visible to MediaMonkey through my FritzBox network, and MM5 tries to communicate with them as DLNA renderers.
Since the RX-V671 is known to send malformed or incomplete DLNA responses, it might cause the Chromium renderer to hang or crash when the device list is refreshed.

So I'll diconnect these devices and have a look, if the crashes dissapper.