0022459: AV on switching between playing and CD nodes

ID	Project	Category	View Status	Date Submitted	Last Update
0022459	MMW 5	Other	public	2026-10-21 16:43	2026-10-30 16:12

Reporter	lowlander	Assigned To
Priority	high	Severity	crash	Reproducibility	random
Status	resolved	Resolution	reopened
Platform	Windows	OS	-	OS Version	11
Product Version	2027.0
Target Version	2027.0	Fixed in Version	2027.0

Summary	0022459: AV on switching between playing and CD nodes
Description	Not experienced an AV before, but on clicking between CD and Playing node an AV occurs. G drive had finished ripping, and CD had been ejected. Drive still showed in MediaMonkey. A new CD was inserted in the F drive. When switching from Playing to F an AV occurred.
Tags	No tags attached.
Attached Files	image.png (10,984 bytes) image.png (10,984 bytes)

Fixed in build	3527

Ludek 2026-10-21 20:31 developer ~0083136 Last edited: 2026-10-21 20:32	Based on log analyzing and tracing the AV address this has been already fixed (SVN revision 46633) in 3527

peke 2026-10-28 00:34 developer ~0083323	Verified 3529

lowlander 2026-10-29 19:00 developer ~0083371	Unsure if it's the same, but experienced a freeze in MM (no AV) with ejecting and inserting a CD. Log added.

Ludek 2026-10-30 16:10 developer ~0083392	I’d keep the original AV marked fixed and track this freeze separately, cross-linked to 0022459. A dump captured while frozen is needed to establish the cause. Please make process dump (.dmp) --> snapshot of MediaMonkey’s memory and threads while it is frozen. It lets us inspect where the UI thread is stuck and what it might be waiting for—information the debug log doesn’t contain. 1. Leave MediaMonkey frozen; don’t terminate or restart it yet. 2. Open Task Manager (Ctrl+Shift+Esc) → Details. 3. Right-click each MediaMonkey process and choose Create memory dump file (wording varies by Windows version). 4. Save the resulting .dmp files from the location Task Manager displays. Microsoft documents this capture method here. 5. Send the compressed dumps together with the debug log and exact MM build number. Capturing both processes ensures we get the renderer that hosts the UI.