MM5 crashes while autotagging and switching to main screen

Report bugs & feature requests for MediaMonkey 5 and learn about the newest builds.

Moderator: Gurus

aboelen
Posts: 11
Joined: Sun Feb 01, 2009 1:52 pm
Location: Netherlands

MM5 crashes while autotagging and switching to main screen

Post by aboelen » Thu May 28, 2020 9:10 am

L.S.,

When auto-tagging a bunch of files and then switching back to the MM5 main screen to check on other tracks, the program crashes.
I select a set of (approx 20) tracks and select auto-tag in the menu. Tagging starts as expected. Then I want to go back to the main screen while auto-tagging is ongoing. I open - in this case - artist view and try to scroll down, MM5 becomes unresponsive (I have now approx 2000 artists in the list so a little lag is not uncommon) and after a while an error message pops up. In this case with log ID 8D508E15. When I go back to the auto-tag window the content is unresponsive, although I can manage window size etc. Then I have to restart MM5.
This error repeats every several auto-tag actions; I have no exact count. Might be the number of files tagged or the number of auto-tagging actions though. I will keep count next time :-?.

When I try to restart the program another error pops up this time with log nr 5C630000. These two might be related. Both the MM5 main screen and the auto-tagging window are white and unresponsive. I then can only kill the program using process explorer.

regards,
AJB
Happy Gold User since 2008 :D
MM version: newest v5 beta & MM server beta alongside latest v4 (MediaMonkey for Windows 4.1.x)
Main Device: Win10, x64, Intel i7, 10Gb RAM, 500Gb SSD Sys + 8Tb HDD data
Media Collection: music (>100.000 Tracks), audiobooks (>10.000 tracks), podcasts (>15.000 tracks) & video (>2500 movies)
MM database on local machine, media files for maintenance on local machine, operational media on Synology NAS 418p - feeding Squeeze players, Apple TV, Google ChromeCast, Synology audio & video players & several iPhones, iPads & Android devices.

aboelen
Posts: 11
Joined: Sun Feb 01, 2009 1:52 pm
Location: Netherlands

Re: MM5 crashes while autotagging and switching to main screen

Post by aboelen » Sun May 31, 2020 8:23 am

Another crash when autotagging (crashlog ID 307D71DF)

I was auto-tagging one directory, then heading back to the mainscreen, autotagged a few more files while the first auto-tag was still in progress. Then, when doing a file reorder based on tags, the original tagging window came to the front flashing with the background of the renaming window. MM5 became unresponsive including no respons on the restartbutton in the error-window. After trying to restart another errorlog (5C630000) was generated. flashing continued but now with a white screen (icon flashes orange white screen flashes between grey edges and full white). Then I killed MM5.
Happy Gold User since 2008 :D
MM version: newest v5 beta & MM server beta alongside latest v4 (MediaMonkey for Windows 4.1.x)
Main Device: Win10, x64, Intel i7, 10Gb RAM, 500Gb SSD Sys + 8Tb HDD data
Media Collection: music (>100.000 Tracks), audiobooks (>10.000 tracks), podcasts (>15.000 tracks) & video (>2500 movies)
MM database on local machine, media files for maintenance on local machine, operational media on Synology NAS 418p - feeding Squeeze players, Apple TV, Google ChromeCast, Synology audio & video players & several iPhones, iPads & Android devices.

Ludek
Posts: 3379
Joined: Fri Mar 09, 2007 9:00 am

Re: MM5 crashes while autotagging and switching to main screen

Post by Ludek » Mon Jun 01, 2020 4:49 am

Thanks for reporting.

Should be fixed in upcoming builds.
Let us know your test results with the new build (once is available).

aboelen
Posts: 11
Joined: Sun Feb 01, 2009 1:52 pm
Location: Netherlands

Re: MM5 crashes while autotagging and switching to main screen

Post by aboelen » Fri Jun 05, 2020 9:41 am

Also with version 5.0.0.2255 MM5 crashes when auto-tagging and then perform other tasks in MM. In this case renaming files based on their tags (not in any way related to the files being auto-tagged). Crashes do not occur always but after having been auto-tagging a range of files. I tried to keep a count but have no exact number. It was between 30 and 50 auto-tags in 4 different runs.
With the crash the auto-tag window and the rename window seem to battle for being the frontmost window. They both lose... that is, they become both unresponsive and I have to kill MM5 with process explorer. The restart button on the error handling window produces error ID 5C630000 and two alternating white windows...

The error window indicated the error-ID would be copied to memory... this is what Ctrl-V reproduces (obviously not only the code itself):

Code: Select all

--------------------------------------------------------------------------------------------------------------------------------------------------------------------
|Methods |Details|Stack   |Address |Module               |Offset  |Unit             |Class            |Procedure/Method                                 |Line      |
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
|*Exception Thread: ID=21060; Parent=0; Priority=0                                                                                                                 |
|Class=; Name=MAIN                                                                                                                                                 |
|DeadLock=0; Wait Chain=                                                                                                                                           |
|Comment=                                                                                                                                                          |
|------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|7FFFFFFE|01     |00000000|096C67E2|libcef.dll           |01B467E2|                 |                 |                                                 |          |
|00000008|04     |0019DBD0|0077CDE0|MediaMonkeyEngine.exe|0037CDE0|EExceptionManager|                 |CreateNewExceptionInfo                           |1473[0]   |
|00000008|04     |0019DBD0|0077D564|MediaMonkeyEngine.exe|0037D564|EExceptionManager|                 |InternalInfo                                     |1657[13]  |
|00000008|04     |0019DBF4|0077D5E4|MediaMonkeyEngine.exe|0037D5E4|EExceptionManager|                 |InternalInfo                                     |1667[23]  |
|00000008|04     |0019DBF4|0077D5D8|MediaMonkeyEngine.exe|0037D5D8|EExceptionManager|                 |InternalInfo                                     |1664[20]  |
|00000008|04     |0019DC34|0077D74B|MediaMonkeyEngine.exe|0037D74B|EExceptionManager|TExceptionManager|Info                                             |1706[33]  |
|00000008|04     |0019DC60|0077DAA2|MediaMonkeyEngine.exe|0037DAA2|EExceptionManager|TExceptionManager|Info                                             |1795[18]  |
|00000008|04     |0019E334|0077D9C4|MediaMonkeyEngine.exe|0037D9C4|EExceptionManager|TExceptionManager|Info                                             |1777[0]   |
|00000008|04     |0019E334|0077DB5E|MediaMonkeyEngine.exe|0037DB5E|EExceptionManager|TExceptionManager|Info                                             |1816[7]   |
|00000008|04     |0019E358|0077DB24|MediaMonkeyEngine.exe|0037DB24|EExceptionManager|TExceptionManager|Info                                             |1809[0]   |
|00000008|04     |0019E358|00A6EADE|MediaMonkeyEngine.exe|0066EADE|EAppCEF          |                 |throwELException                                 |261[1]    |
|00000008|04     |0019E370|00A6EAC8|MediaMonkeyEngine.exe|0066EAC8|EAppCEF          |                 |throwELException                                 |260[0]    |
|00000008|04     |0019E370|00A6FEC6|MediaMonkeyEngine.exe|0066FEC6|ExceptionHandler |                 |MyExceptHandler                                  |394[6]    |
|00000008|03     |0019E4D8|77A3EC20|ntdll.dll            |0003EC20|ntdll            |                 |RtlReleaseSRWLockExclusive                       |          |
|00000008|03     |0019E544|77A67BF5|ntdll.dll            |00067BF5|ntdll            |                 | (possible RtlGetAppContainerNamedObjectPath+181)|          |
|00000008|03     |0019E544|77A67BEF|ntdll.dll            |00067BEF|ntdll            |                 | (possible RtlGetAppContainerNamedObjectPath+175)|          |
|00000008|03     |0019E670|77A7205A|ntdll.dll            |0007205A|ntdll            |                 |ZwQueryVirtualMemory                             |          |
|00000008|03     |0019E674|77A72050|ntdll.dll            |00072050|ntdll            |                 |ZwQueryVirtualMemory                             |          |
|00000008|03     |0019E674|7657FC89|KERNELBASE.dll       |0010FC89|KERNELBASE       |                 |VirtualQuery                                     |          |
|00000008|03     |0019E69C|772377E0|kernel32.dll         |000177E0|KERNEL32         |                 |VirtualQuery                                     |          |
|00000008|04     |0019E69C|00633CEE|MediaMonkeyEngine.exe|00233CEE|ELowLevel        |                 |GetReadableSize                                  |1563[11]  |
|00000008|04     |0019E6E0|00633D22|MediaMonkeyEngine.exe|00233D22|ELowLevel        |                 |GetReadableSize                                  |1570[18]  |
|00000008|04     |0019E714|006B4BF0|MediaMonkeyEngine.exe|002B4BF0|EThreadsManager  |                 |IsOutputDebugStringException                     |1472[0]   |
|00000008|04     |0019E714|00A6C1E1|MediaMonkeyEngine.exe|0066C1E1|EExceptionHook   |                 |HandleThisException                              |160[20]   |
|00000008|04     |0019E724|00409C40|MediaMonkeyEngine.exe|00009C40|System           |                 |_UStrClr                                         |23832[0]  |
|00000008|04     |0019E724|0040B894|MediaMonkeyEngine.exe|0000B894|System           |                 |_FinalizeArray                                   |31131[80] |
|00000008|03     |0019E770|77A343A0|ntdll.dll            |000343A0|ntdll            |                 |RtlImageNtHeaderEx                               |          |
|00000008|03     |0019E770|77A31726|ntdll.dll            |00031726|ntdll            |                 | (possible LdrFindResource_U+438)                |          |
|00000008|03     |0019E7A0|77A316E9|ntdll.dll            |000316E9|ntdll            |                 | (possible LdrFindResource_U+377)                |          |
|00000008|03     |0019E7A0|77A2BF56|ntdll.dll            |0002BF56|ntdll            |                 |RtlImageDirectoryEntryToData                     |          |
|00000008|03     |0019E7B8|77A2BF40|ntdll.dll            |0002BF40|ntdll            |                 |RtlImageDirectoryEntryToData                     |          |
|00000008|03     |0019E7B8|77A2E0A6|ntdll.dll            |0002E0A6|ntdll            |                 | (possible LdrResFindResourceDirectory+2822)     |          |
|00000008|03     |0019E7E8|77A2E012|ntdll.dll            |0002E012|ntdll            |                 | (possible LdrResFindResourceDirectory+2674)     |          |
|00000008|04     |0019E7F8|00405778|MediaMonkeyEngine.exe|00005778|System           |                 |SysFreeMem                                       |2900[0]   |
|00000008|04     |0019E7F8|00406A08|MediaMonkeyEngine.exe|00006A08|System           |                 |_FreeMem                                         |4364[20]  |
|00000008|04     |0019E7FC|00409CC1|MediaMonkeyEngine.exe|00009CC1|System           |                 |_UStrArrayClr                                    |23997[16] |
|00000008|04     |0019E808|017618C3|MediaMonkeyEngine.exe|013618C3|AppInitCode      |                 |doAppInitialize                                  |1441[240] |
|00000008|04     |0019E80C|0040F475|MediaMonkeyEngine.exe|0000F475|SysInit          |                 |InitThreadTLS                                    |632[15]   |
|00000008|04     |0019E80C|00409184|MediaMonkeyEngine.exe|00009184|System           |                 |_HandleFinally                                   |19135[40] |
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
Happy Gold User since 2008 :D
MM version: newest v5 beta & MM server beta alongside latest v4 (MediaMonkey for Windows 4.1.x)
Main Device: Win10, x64, Intel i7, 10Gb RAM, 500Gb SSD Sys + 8Tb HDD data
Media Collection: music (>100.000 Tracks), audiobooks (>10.000 tracks), podcasts (>15.000 tracks) & video (>2500 movies)
MM database on local machine, media files for maintenance on local machine, operational media on Synology NAS 418p - feeding Squeeze players, Apple TV, Google ChromeCast, Synology audio & video players & several iPhones, iPads & Android devices.

Peke
Posts: 13282
Joined: Tue Jun 10, 2003 7:21 pm
Location: Serbia
Contact:

Re: MM5 crashes while autotagging and switching to main screen

Post by Peke » Sat Jun 06, 2020 7:35 am

Hi,
Unfortunately LOG file do not show much.
I tried to replicate the bug yesterday for 2h without success, at one moment I had 10 Auto-Tag queue.

Can you please let me know if you have multiple auto-Tag windows open?

We need any specific steps in order to add additional debug messages and cath more precise point of crash occurrences.
Best regards,
Pavle
MediaMonkey Team lead QA/Tech Support guru
Admin of Free MediaMonkey addon Site HappyMonkeying
Image
Image
How to add SCREENSHOTS to forum

aboelen
Posts: 11
Joined: Sun Feb 01, 2009 1:52 pm
Location: Netherlands

Re: MM5 crashes while autotagging and switching to main screen

Post by aboelen » Sun Jun 07, 2020 6:03 pm

Pavle,

At the moment of the crash I had only one auto-tag window running. I pushed [OK] on the renaming window. Then that window and the auto-tag started to alternate. I had run several other auto-tags before that moment but these where all ready and closed.
I will do a run tomorrow with a Windows debugger open in the background (to provide some extra debug info). I will try to log more accurate, the number of auto-tags done and/or screens open when the error reappears.
The error feels like a buffer overrun. Might it work to enhance the buffer space? Is there a startup parameter I can provide to MM5 that does that? What is the default buffer space or is it assigned dynamically. Perhaps I should lower the buffer space first to see whether the error appears earlier. Then it is more likely that the issue is connected to buferring.

Regards,
Alexander
Happy Gold User since 2008 :D
MM version: newest v5 beta & MM server beta alongside latest v4 (MediaMonkey for Windows 4.1.x)
Main Device: Win10, x64, Intel i7, 10Gb RAM, 500Gb SSD Sys + 8Tb HDD data
Media Collection: music (>100.000 Tracks), audiobooks (>10.000 tracks), podcasts (>15.000 tracks) & video (>2500 movies)
MM database on local machine, media files for maintenance on local machine, operational media on Synology NAS 418p - feeding Squeeze players, Apple TV, Google ChromeCast, Synology audio & video players & several iPhones, iPads & Android devices.

Peke
Posts: 13282
Joined: Tue Jun 10, 2003 7:21 pm
Location: Serbia
Contact:

Re: MM5 crashes while autotagging and switching to main screen

Post by Peke » Sun Jun 07, 2020 8:05 pm

Hi,
I agree with your assumption. It looks like buffer overrun, and maybe my PC is problematic (AMD 2700x, 64GB RAM, 970 Pro NVMe) so my buffers clean them self more efficiently :(

Let see if we can catch it this time.
Best regards,
Pavle
MediaMonkey Team lead QA/Tech Support guru
Admin of Free MediaMonkey addon Site HappyMonkeying
Image
Image
How to add SCREENSHOTS to forum

Lowlander
Posts: 47545
Joined: Sat Sep 06, 2003 5:53 pm
Location: MediaMonkey 5

Re: MM5 crashes while autotagging and switching to main screen

Post by Lowlander » Thu Jul 09, 2020 6:52 pm

I'm not able to reproduce with 2259.
Lowlander (MediaMonkey user since 2003)

Post Reply