Expanding Collapsed Playlist Shows Runtime Error

[Dryst]

This issue has been happening for many versions. I have observed it in all 2024 versions, and I just reproduced it in the latest MediaMonkey_2024.0.0.3018. I was hoping this would have been fixed by now, but it is still present.

Click a collapsed playlist item in the tree to the left to see the error upon application start:

https://www.dropbox.com/scl/fi/5azjskeq ... oxszq&dl=0

Clicking continue shows the next runtime error:

https://www.dropbox.com/scl/fi/5btltu9f ... 6xkm4&dl=0

[Lowlander]

This hasn't been reported before, nor can I reproduce this. Please capture this in a debug log (step 4b) and attach the log to a Support Ticket: https://www.mediamonkey.com/forum/viewtopic.php?t=86643

[Dryst]

Yes -- I will install the debug version again.

I do have ideas on why I am facing these issues though. My CPU is the latest Intel i9. I think the issue I face may be thread related.

[Dryst]

Looking at Windows Event Viewer, I see the following two entries:

source: Application Error

Code: Select all

Faulting application name: MediaMonkeyEngine.exe, version: 2024.0.0.3018, time stamp: 0x662bdca5
Faulting module name: KERNELBASE.dll, version: 10.0.22621.3447, time stamp: 0x67ef8931
Exception code: 0x0eedfade
Fault offset: 0x001498b2
Faulting process id: 0x0x384C
Faulting application start time: 0x0x1DA9A0B4144C908
Faulting application path: C:\Program Files (x86)\Ventis\MediaMonkey\MediaMonkeyEngine.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 9856b58d-2cb5-4a67-9773-583a4a402ace
Faulting package full name: 
Faulting package-relative application ID: 

source: Windows Error Reporting

Code: Select all

Fault bucket 1537547253124291132, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: MediaMonkeyEngine.exe
P2: 2024.0.0.3018
P3: 662bdca5
P4: KERNELBASE.dll
P5: 10.0.22621.3447
P6: 67ef8931
P7: 0eedfade
P8: 001498b2
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.5ba26a34-f826-474f-bb6f-0f2abc8bdc59.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.10ee21d6-c9a1-4829-a936-6788f5f6057b.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.19a057ae-da97-4b39-8fc2-22ea67c37c67.tmp.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_MediaMonkeyEngin_c688547dc694622c9bbb58677d494717f805f6c_7f61c1c6_fbb3869d-fd4f-4b33-9ca1-5ec741e94589

Analysis symbol: 
Rechecking for solution: 0
Report Id: 9856b58d-2cb5-4a67-9773-583a4a402ace
Report Status: 268435456
Hashed bucket: 1c56a75372e5e4252556771497d9da3c

This is a familiar error that I have seen running all versions of MMW5. It could very well be that this was the true issue, and the NULL Runtime error is a result of this crash.

[Peke]

Hi,
Kernel errors usually are not related to APP itself and have much deeper cause, both hardware and OS itself. Crash appears initiated from OS side.

[Dryst]

Okay.

There's a compatibility issue specific to MMW5 on Windows 11 Professional running new hardware with the latest of all drivers.

MMW4 does not face this issue ironically. It runs perfectly.

[Peke]

Hi,
Hmmm, interesting only thing that is major difference from MM4 is that MM5/2024 uses GUI that take all advantage of GPU Hardware acceleration to visually improve MM UI.

Can you open support ticket I would like to get to bottom of this especially as MM 2024 uses latest Chromium Rendering engine for UI.