View Issue Details

IDProjectCategoryView StatusLast Update
0021201MMW 5Burning / Disc Handlingpublic2024-10-15 22:46
Reporterlowlander Assigned To 
PriorityurgentSeveritycrashReproducibilityrandom
Status closedResolutionreopened 
Product Version2024.0 
Target Version2024.0Fixed in Version2024.0 
Summary0021201: Invalid Pointer Operation on close of Properties on CD edit
DescriptionOccasionally MediaMonkey either throws an error or closes itself on editing via Properties of a CD. This seems to be happening to Audiobooks that have not online metadata.
Steps To Reproduce1 Insert CD
2 Select all files
3 Edit Album and Disc# via Properties of all files on CD
4 OK Properties
--> Immediate crash
--> Playback continues on Continue
TagsNo tags attached.
Attached Files
image.png (6,958 bytes)   
image.png (6,958 bytes)   
Fixed in build3063

Relationships

related to 0020836 closedLudek 4A750000 on CD Properties edit 
related to 0016833 closedLudek Tree Node: Audio CD info in Tree node is not updated when info is edited in Track Browser 

Activities

Ludek

2024-09-13 13:17

developer   ~0076929

Fixed in 3053

lowlander

2024-09-17 04:45

developer   ~0076995

No method to reproduce, will reopen if this happens again.

lowlander

2024-09-17 15:28

developer   ~0077003

It happened again on 3054. Log added (occurs at end of log).

Ludek

2024-09-17 18:58

developer   ~0077017

The log is really huge (more than 3 millions of lines) and at the end I really see "Invalid pointer operation" when writing to
Z:\MediaMonkey\Portable\CDPlayer.ini

But I can't see the callstack as no crash log has been generated, just freeze log in OutputDebugString when you were closing the massive DbgView ouput..
Going to re-analyze code for the possible fix..

Ludek

2024-09-17 20:05

developer   ~0077019

OK, I found a code glitch that probably caused this crash, please re-test

=> Fixed in 3055

peke

2024-09-19 10:52

developer   ~0077060

Verified 3055

lowlander

2024-10-10 04:38

developer   ~0077234

Unfortunately no log, but this was seen again on 3062.

Ludek

2024-10-10 15:44

developer   ~0077238

ok, it's hard to fix something without log, but I revised the previous logs and found another code glitch that could be the cause..

Fixed in 3063.

rusty

2024-10-15 19:51

administrator   ~0077295

Unable to replicate in 3064. Leaving as 'resolved' for LL to reverify.

lowlander

2024-10-15 22:46

developer   ~0077303

Tested with 20 discs on 3064 and didn't observe this.