[1399] Out Of Memory and Access Violation [#8084]
Posted: Fri Jul 01, 2011 6:52 pm
MM4 1399 is running under Win 7 x64 with i7 2500 processor and 8 GB of RAM
When attempting to change the rating of an ALAC file that is playing, using the debug version of MM4.
9 times outs of 10 I get an "Access violation in Module f_aac_codec.dll" error box. Selecting the "OK" or red "x" simply regenerates the access violation box. Occasionally I will receive and "Out Of Memory" error box, and selecting "OK" results in the "Access violation..." error box described above (with the same results).
After a couple regenerations, the access voiolation error switches to "ntdll", and after a couple more, the access violation cites mediamonkey.exe.
MM4 is locked up at the point of the first dialog box and can only be shut down through task manager.
I have had only one instance of this failure where a debug file was automatically generated and sent. Normally the program simply locks up.
Additional Info July 3rd, 2011
This problem also occurs when editing any ALAC tag info (date, album art, album, etc.) while the track is playing. Once the error boxes occur, the track continues to play, but within 10 seconds or so, produces digital noise only, and then loops back to the point where the error box appeared.
Also, MM4 is set up to run as administrator on Windows 7.
This problem does not occur with MM3 3.2.5.1306
debugview.exe log file posted via service ticket KPK-545516
When attempting to change the rating of an ALAC file that is playing, using the debug version of MM4.
9 times outs of 10 I get an "Access violation in Module f_aac_codec.dll" error box. Selecting the "OK" or red "x" simply regenerates the access violation box. Occasionally I will receive and "Out Of Memory" error box, and selecting "OK" results in the "Access violation..." error box described above (with the same results).
After a couple regenerations, the access voiolation error switches to "ntdll", and after a couple more, the access violation cites mediamonkey.exe.
MM4 is locked up at the point of the first dialog box and can only be shut down through task manager.
I have had only one instance of this failure where a debug file was automatically generated and sent. Normally the program simply locks up.
Additional Info July 3rd, 2011
This problem also occurs when editing any ALAC tag info (date, album art, album, etc.) while the track is playing. Once the error boxes occur, the track continues to play, but within 10 seconds or so, produces digital noise only, and then loops back to the point where the error box appeared.
Also, MM4 is set up to run as administrator on Windows 7.
This problem does not occur with MM3 3.2.5.1306
debugview.exe log file posted via service ticket KPK-545516