by CrashMonkey » Tue Oct 24, 2023 5:49 pm
Did a second run with the exact the same songs, because something strange happend during the 3th batch in first run.
Explorer.exe crashed suddenly. WhoCrashed told me that destructor'.sys was the culprint.
I guess somewhere is destructor called but then in code as 'destructor'' <-- one quite --> ' <-- to much? (both crashes caused by the same thing)
To be sure if it was mediamonkey, i did the re-run.
At the 3th set of 201 of 300 from 1000, it made it crash again around track 28. This happend at the first run at around the same track.
When i read the GC failed, i read it as Garbage Collector? I am i right?
Then i guess the instance before that the GC failed maybe to destuct the items, resulting in my explorer crash, and the next time it ran, it could not allocate because it was not destroyed before? Resulting on white screen of death.
The two above lines of text are a guess.
I did this run, without the debugview. Without debug view autolabel header does update ok. Tomorrow a run again with the debugview confirming once again if all turns out the same.
One more annoyance, when its autolabeling is going. And while i write this, with every track change, the focus goes off my google chrome for 1 sec, and i cannot type, then focus comes back and i can type again. This happens also when i go to a other application.
And while i write this the focus went out of my browser back to MM, and it crached with a white screen. On the end of the 3th run again.
Will do this tomorrow again, and i will install a video recording tool, to demonstrate it in a video. (As for a other strange behaiver i might need it as well, to show whats going on. But that occurs on a more rare basis)
Edit: In version 5 of MM, the behaivor is that the entire app crashes. Thats why i am testing it now in 5.1
Did a second run with the exact the same songs, because something strange happend during the 3th batch in first run.
Explorer.exe crashed suddenly. WhoCrashed told me that destructor'.sys was the culprint.
I guess somewhere is destructor called but then in code as 'destructor'' <-- one quite --> ' <-- to much? (both crashes caused by the same thing)
To be sure if it was mediamonkey, i did the re-run.
At the 3th set of 201 of 300 from 1000, it made it crash again around track 28. This happend at the first run at around the same track.
When i read the GC failed, i read it as Garbage Collector? I am i right?
Then i guess the instance before that the GC failed maybe to destuct the items, resulting in my explorer crash, and the next time it ran, it could not allocate because it was not destroyed before? Resulting on white screen of death.
The two above lines of text are a guess.
I did this run, without the debugview. Without debug view autolabel header does update ok. Tomorrow a run again with the debugview confirming once again if all turns out the same.
One more annoyance, when its autolabeling is going. And while i write this, with every track change, the focus goes off my google chrome for 1 sec, and i cannot type, then focus comes back and i can type again. This happens also when i go to a other application.
And while i write this the focus went out of my browser back to MM, and it crached with a white screen. On the end of the 3th run again.
Will do this tomorrow again, and i will install a video recording tool, to demonstrate it in a video. (As for a other strange behaiver i might need it as well, to show whats going on. But that occurs on a more rare basis)
Edit: In version 5 of MM, the behaivor is that the entire app crashes. Thats why i am testing it now in 5.1