[Solved in 2526] MM5.2503 Auto-tag unusable at the moment

Help improve MediaMonkey 5 by testing the latest pre-release builds, and reporting bugs and feature requests.

Moderator: Gurus

Friedrich
Posts: 176
Joined: Sat Mar 01, 2008 3:14 am

[Solved in 2526] MM5.2503 Auto-tag unusable at the moment

Post by Friedrich »

Rusty had this "Metadata lookup undefined" already reported in:
https://www.ventismedia.com/mantis/view.php?id=18316

But here its more serious than just failing to auto tag.
The first time in a MM session using auto-tag lookup simply results in "failed" and can be closed by "cancel".
But after the second or third time MM completely crashes "not responding" and has to be forcefully closed.
Several auto-generated reports have been sent.
Let me know if you need something tried.
Last edited by Friedrich on Thu Dec 09, 2021 10:39 am, edited 1 time in total.
MM5 (2606)and MM4 (1919) installed and running well on:
Debian 11 KDE, EndeavourOS KDE (wine 7.4 via playonlinux), Win10 64bit
PetrCBR
Posts: 1763
Joined: Tue Mar 07, 2006 5:31 pm
Location: Czech
Contact:

Re: MM5.2503 Auto-tag unusable at the moment

Post by PetrCBR »

Will check your bugreport. Thanks for a feedback.
How to make a debuglog - step 4b: viewtopic.php?f=30&t=86643
Friedrich
Posts: 176
Joined: Sat Mar 01, 2008 3:14 am

MM5.2508 Auto-tag still crashing MM

Post by Friedrich »

Seems unchanged here since 2503:
viewtopic.php?f=30&t=100131
Anyone else having the same problem?
MM5 (2606)and MM4 (1919) installed and running well on:
Debian 11 KDE, EndeavourOS KDE (wine 7.4 via playonlinux), Win10 64bit
Peke
Posts: 17446
Joined: Tue Jun 10, 2003 7:21 pm
Location: Earth
Contact:

Re: MM5.2508 Auto-tag still crashing MM

Post by Peke »

Hi,
Due the recent changes in 2508 I have tested Auto Tag extensively past few days and, no crashes happen on 10-1000 tracks in Auto Tag.

Can you please open support ticket and supply debug log with crash in it as described here viewtopic.php?f=30&t=86643 so that we cn analyze why it crashes on your system.
Best regards,
Peke
MediaMonkey Team lead QA/Tech Support guru
Admin of Free MediaMonkey addon Site HappyMonkeying
Image
Image
Image
How to attach PICTURE/SCREENSHOTS to forum posts
Friedrich
Posts: 176
Joined: Sat Mar 01, 2008 3:14 am

Re: MM5.2508 Auto-tag still crashing MM

Post by Friedrich »

[Ticket #2883] opened with the latest log-id.
1 or 2 autogenerated logs referring to auto-tagging problems had also been sent previously.
Sometimes its complete "white out" though and no auto-log dialog appears.
MM5 (2606)and MM4 (1919) installed and running well on:
Debian 11 KDE, EndeavourOS KDE (wine 7.4 via playonlinux), Win10 64bit
Peke
Posts: 17446
Joined: Tue Jun 10, 2003 7:21 pm
Location: Earth
Contact:

Re: MM5.2503 Auto-tag unusable at the moment

Post by Peke »

Hi,
Can you please rename "persistent.json" to "1Persistent.json", delete "Persistent.json.bck"" and start MM5 to see if crash still occurs?
Best regards,
Peke
MediaMonkey Team lead QA/Tech Support guru
Admin of Free MediaMonkey addon Site HappyMonkeying
Image
Image
Image
How to attach PICTURE/SCREENSHOTS to forum posts
Friedrich
Posts: 176
Joined: Sat Mar 01, 2008 3:14 am

Re: MM5.2503 Auto-tag unusable at the moment

Post by Friedrich »

Peke wrote: Sat Oct 09, 2021 3:26 pm Can you please rename "persistent.json" to "1Persistent.json", delete "Persistent.json.bck"" and start MM5 to see if crash still occurs?
Still occurs. No difference.
Latest: 4E550000
P.S.:
1. In a win10 virtual machine (virtualbox/Debian11): same problem
MM5 (2606)and MM4 (1919) installed and running well on:
Debian 11 KDE, EndeavourOS KDE (wine 7.4 via playonlinux), Win10 64bit
Friedrich
Posts: 176
Joined: Sat Mar 01, 2008 3:14 am

Re: MM5.2503 Auto-tag unusable at the moment

Post by Friedrich »

Update: Problem persists in 2516.
Happening so far in:
1. This machines win10 installation, 2. a virtualbox win 10, 3. a virtualbox win7 and 4. a fresh win10 install on a different machine.
As written in the support ticket here are the steps to reproduce this:

After selecting a track and hitting auto-tag:
1. let auto-tag til finished ("done" or "fail")
2. Hit "Cancel"
3. Repeat auto-tag with the same selected file til finished ("done" or "fail")
4. Hit "Cancel"
5. Repeat auto-tag a third time
Result:
The auto-tag window is empty of track(s); buttons and description above remain
The auto-generated debug-log appears after a while and was send
6. Hit "Cancel" button in auto-tag window or wait.
Result: crash/white out

Maybe someone else is able to reproduce.. .
MM5 (2606)and MM4 (1919) installed and running well on:
Debian 11 KDE, EndeavourOS KDE (wine 7.4 via playonlinux), Win10 64bit
Peke
Posts: 17446
Joined: Tue Jun 10, 2003 7:21 pm
Location: Earth
Contact:

Re: MM5.2503 Auto-tag unusable at the moment

Post by Peke »

Hi,
Can you replicate same if you physically access PS (I guess 1. and 4. are physical one). I can't replicate using VMWare and RDP to either Physical PCs or remote using for example AnyDesk.

EDIT: I am suspecting Some sort of Rendering problem. Try to locate eureka log files from crash as described at viewtopic.php?f=30&t=86643 because they could help see where crash happen.
Best regards,
Peke
MediaMonkey Team lead QA/Tech Support guru
Admin of Free MediaMonkey addon Site HappyMonkeying
Image
Image
Image
How to attach PICTURE/SCREENSHOTS to forum posts
Friedrich
Posts: 176
Joined: Sat Mar 01, 2008 3:14 am

Re: MM5.2503 Auto-tag unusable at the moment

Post by Friedrich »

Hi, Peke
Peke wrote: Mon Nov 08, 2021 7:10 am Can you replicate same if you physically access PS
Please, explain what you mean by: "physically access PS".
(I guess 1. and 4. are physical one).
Yes, 1 and 4 are physical ones. (2 and 3 are virtual machines (virtualbox))
I can't replicate using VMWare and RDP to either Physical PCs or remote using for example AnyDesk.
I haven't tried that.
To give you a visual impression what I meant by
Friedrich wrote:The auto-tag window is empty of track(s); buttons and description above remain
https://ibb.co/VBXmTt6
EDIT: I am suspecting Some sort of Rendering problem.
Rendering problem definitely seems at least part of the problem:
Just finished a fifth test on a friends "Surface Pro":
Took maybe a few more auto-tag/cancel cycles to reproduce.
But only in this last test-case even the win 10 task-manager (necessary to kill the MM5 process) suffered from some rendering problems; apart from the usual "white-out".
Try to locate eureka log files from crash as described at viewtopic.php?f=30&t=86643 because they could help see where crash happen.
Eureka log is empty; auto-generated logs usually work.
MM5 (2606)and MM4 (1919) installed and running well on:
Debian 11 KDE, EndeavourOS KDE (wine 7.4 via playonlinux), Win10 64bit
Post Reply