MM5 5.0.4.2690: Task queue deadlock detected (0AF10000) [#19823]

[TekGamer]

MediaMonkey 5.0.4.2690 (Portable Mode)

I keep getting this error randomly, then MM5 locks up and I have to kill the process via TaskManager

Code: Select all

Task queue deadlock detected (N:\Delphi\MediaMonkey5042\HTML5Monkey\Workers.pas, line 834

It is worth nothing that my MM5 portable installation runs from the J:\MediaMonkey5 directory, yet there is a reference in the error to an N:\ drive.

[Peke]

Hi,
Is there any way to tie it to repeated actions you have done in MM that precedes deadlock?

eg. Track conversation, tree node creation, search, casting, ... ?

Added as https://www.ventismedia.com/mantis/view.php?id=19823

It is worth nothing that my MM5 portable installation runs from the J:\MediaMonkey5 directory, yet there is a reference in the error to an N:\ drive.

NOTE: Crashlogs point to path to source code on development platform so that devs can easily locate exact point in source code in order to debug it.

[Ludek]

We have 0AF10000 here, but it is from version 5.0.4.2659
Is it your log?

-- If no then please submit the log
-- If yes, then please upgrade to version 5.0.4.2690 to see whether you are still seeing it then?

[TekGamer]

I am definitely on 5.0.4.2690 and have been since the end of November when it was released... how do I send logs if when I go to Help... Debug... Send Logs I get a "User exception (E7FE0000)" error?

[TekGamer]

Hi,
Is there any way to tie it to repeated actions you have done in MM that precedes deadlock?

eg. Track conversation, tree node creation, search, casting, ... ?

Added as https://www.ventismedia.com/mantis/view.php?id=19823

It is worth nothing that my MM5 portable installation runs from the J:\MediaMonkey5 directory, yet there is a reference in the error to an N:\ drive.

NOTE: Crashlogs point to path to source code on development platform so that devs can easily locate exact point in source code in order to debug it.

I am still not sure what action is causing the error, I was just browsing the Folders tree when the error occurred.

[Ludek]

HI, once you are on debug build now (and you are as you have the menu Help > Debug) then just wait for the "Task queue deadlock detected" error to happen and crash log will be auto-generated to submit. Then submit it and write the log ID here.

Thanks!

[TekGamer]

HI, once you are on debug build now (and you are as you have the menu Help > Debug) then just wait for the "Task queue deadlock detected" error to happen and crash log will be auto-generated to submit. Then submit it and write the log ID here.

Thanks!

Where is crash log stored? The app locks up on me when the error occurs.

[Ludek]

Wasn't it auto-generated ? But once it failed to submit then you should be able to locate it as MediaMonkeyEngine.EL file on your PC, see item 4A) here for details: viewtopic.php?f=30&t=86643

[TekGamer]

Wasn't it auto-generated ? But once it failed to submit then you should be able to locate it as MediaMonkeyEngine.EL file on your PC, see item 4A) here for details: viewtopic.php?f=30&t=86643

No crash file was auto generated.

I checked in both directories:
%appdata%\EurekaLab s.a.s\EurekaLog\Bug Reports\MediaMonkey.exe
%appdata%\EurekaLab s.a.s\EurekaLog\Bug Reports\MediaMonkeyEngine.exe

I sent you a PM with at least the log that came up in the window that finally appeared after the app froze, I hope that helps!

[Ludek]

I sent you a PM with at least the log that came up in the window that finally appeared after the app froze, I hope that helps!

Hmm, it is a pity that you haven't submitted the 0AF10000 log.
It is not complete in the PM so I cannot see callstacks of individual threads to analyze it.

The last logs submitted from you (user ID: johnq) is one week old, but it is dirfferent log.

[Ludek]

FYI: I have studied log 0AF10000 from another user and I think that it has the same cause.

Fixed it as https://www.ventismedia.com/mantis/view.php?id=19823 for the next build

[TekGamer]

FYI: I have studied log 0AF10000 from another user and I think that it has the same cause.

Fixed it as https://www.ventismedia.com/mantis/view.php?id=19823 for the next build

Ok, thanks!

[kmenzel]

Not meaning to bump uneccesarily, but I think I was potentially the other user hitting this crash, as I see it at least a dozen times daily, and I think I clicked "submit" on a crash or two

I'm glad to hear it's fixed in an upcoming build, if there's anything I can do to help in terms of confirming that this is fixed/providing any additional logs(?) the next time I hit the crash let me know.

Otherwise I'll wait patiently.

I was wondering, since clearly not everyone is hitting this bug, was there a root cause identified that I might be able to... I dunno, avoid? Or change something on my end?

[TekGamer]

Not meaning to bump uneccesarily, but I think I was potentially the other user hitting this crash, as I see it at least a dozen times daily, and I think I clicked "submit" on a crash or two

I'm glad to hear it's fixed in an upcoming build, if there's anything I can do to help in terms of confirming that this is fixed/providing any additional logs(?) the next time I hit the crash let me know.

Otherwise I'll wait patiently.

I was wondering, since clearly not everyone is hitting this bug, was there a root cause identified that I might be able to... I dunno, avoid? Or change something on my end?

I get this error randomly, so, often that MM5 has become unusable for me for several months now. And, most of the time, it locks up to where I cannot submit the crash at all, and have to kill the MM5 processes via Task Manager. There has only been a few times where, if I let it sit for a while I can finally submit a crash log (but then it locks up so I don't even know if it is sending anything). It is not reproducible either, there is no one action I can point to that causes the error. I could be tagging tracks, just playing tracks, or both. It has become so bad that I have just had to resort to using the Windows 11 built-media player just to play tracks while I am sitting back waiting for the new release.

[demopilot208]

I get this error randomly, so, often that MM5 has become unusable for me for several months now. And, most of the time, it locks up to where I cannot submit the crash at all, and have to kill the MM5 processes via Task Manager. There has only been a few times where, if I let it sit for a while I can finally submit a crash log (but then it locks up so I don't even know if it is sending anything). It is not reproducible either, there is no one action I can point to that causes the error. I could be tagging tracks, just playing tracks, or both. It has become so bad that I have just had to resort to using the Windows 11 built-media player just to play tracks while I am sitting back waiting for the new release.

I am also experiencing the same. I try to fill out and send the logs the best I can, but everything freezes/crashes so hard it won't let me even click to do so. It crashes randomly, but I sort of expect it at this point. I hope they'll find a solution soon.