MediaMonkey Corrupts Windows (Explorer) [#21345]

[rusty]

Dypsis, Flex,

Thanks for all the info. We suspect that the reason it's occurring for 3057 and not 3051 is because of the change made in 3054. If our hypothesis is correct, the reason it wouldn't occur on a clean install but would occur on the upgrade from v4 could be because the upgrade has network/drive paths in the config/DB that are somehow triggering the issue.

Could you:
a) Confirm that it doesn't occur with Build 3053
b) Generate a debug log using the most recent beta debug build and share a link to it via the helpdesk?
c) While replicating the issue can you verify whether MMW CPU utilization is increased (in comparison to a build that doesn't trigger the bug)?

Thanks!

-Rusty

[FlexFlexerson]

Dypsis, Flex,

Thanks for all the info. We suspect that the reason it's occurring for 3057 and not 3051 is because of the change made in 3054. If our hypothesis is correct, the reason it wouldn't occur on a clean install but would occur on the upgrade from v4 could be because the upgrade has network/drive paths in the config/DB that are somehow triggering the issue.

Could you:
a) Confirm that it doesn't occur with Build 3053
b) Generate a debug log using the most recent beta debug build and share a link to it via the helpdesk?
c) While replicating the issue can you verify whether MMW CPU utilization is increased (in comparison to a build that doesn't trigger the bug)?

Thanks!

-Rusty

Thanks Rusty.

On (a) I can confirm that the error does not occur in build 3053.

On (b) I tried to generate a debug log when using the most recent build, but because the error messes up my keyboard and mouse buttons, I'm not able to send it (or copy the log or anything else). Not sure how to get around that to send a log.

On (c) CPU utilization was the same comparing both build 3053 and the most recent one.

[rusty]

Hi Flex,

Thanks!
a) This means that it's most likely related to https://www.ventismedia.com/mantis/view.php?id=21202
b) In debugview, before you launch MediaMonkey, click File > Log to File as... (this causes it to save it to the log file in question as the bug occurs--no need to save it afterwards).
c) Interesting. Let's see what the log shows.

Looking forward to hearing back.

Thanks!

-Rusty

[FlexFlexerson]

Hi Flex,

Thanks!
a) This means that it's most likely related to https://www.ventismedia.com/mantis/view.php?id=21202
b) In debugview, before you launch MediaMonkey, click File > Log to File as... (this causes it to save it to the log file in question as the bug occurs--no need to save it afterwards).
c) Interesting. Let's see what the log shows.

Looking forward to hearing back.

Thanks!

-Rusty

Gotcha. Just submitted a ticket with my debug log.

[dypsis]

Dypsis, Flex,

Thanks for all the info. We suspect that the reason it's occurring for 3057 and not 3051 is because of the change made in 3054. If our hypothesis is correct, the reason it wouldn't occur on a clean install but would occur on the upgrade from v4 could be because the upgrade has network/drive paths in the config/DB that are somehow triggering the issue.

Could you:
a) Confirm that it doesn't occur with Build 3053
b) Generate a debug log using the most recent beta debug build and share a link to it via the helpdesk?
c) While replicating the issue can you verify whether MMW CPU utilization is increased (in comparison to a build that doesn't trigger the bug)?

Thanks!

-Rusty

3053 doesn't have this bug either.
So, how do I generate the debug log? Do you want it done with 3074?

[rusty]

flex,

We received the ticket, but the log wasn't attached. Can you share a link to the log (e.g. using dropbox or any other file sharing service) instead via the helpdesk ticket?


dypsis,

It probably wouldn't hurt if you shared a log as well since the cases may be slightly different.

And yes, it would be best to replicate the bug with 3074 debug. In case you didn't see my note above--if debugview isn't allowing you to save the log due to the bug: In debugview, before you launch MediaMonkey, click File > Log to File as... (this causes it to save it to the log file in question as the bug occurs--no need to save it afterwards).

Thanks!

-Rusty

[dypsis]

flex,

We received the ticket, but the log wasn't attached. Can you share a link to the log (e.g. using dropbox or any other file sharing service) instead via the helpdesk ticket?


dypsis,

It probably wouldn't hurt if you shared a log as well since the cases may be slightly different.

And yes, it would be best to replicate the bug with 3074 debug. In case you didn't see my note above--if debugview isn't allowing you to save the log due to the bug: In debugview, before you launch MediaMonkey, click File > Log to File as... (this causes it to save it to the log file in question as the bug occurs--no need to save it afterwards).

Thanks!

-Rusty

Done.

I zipped the logs. I'm not sure if they attach as a bare .log file.

[Ludek]

FYI fixed in 3076 as https://www.ventismedia.com/mantis/view.php?id=21345

[dypsis]

3076 is NOT working with the installer you sent me.

Did you replace the correct file in the installer?

This is the file that is working for me.

MediaMonkeyEngine.exe
Size: 32.9 MB
CRC32: 30398EA0
MD5: BE144AC17964917DB76DF5A4B0521A91
SHA-1: A753226600E3A909B4244A60A06C3103212DFAAE

I have just tested it again with the above file, and it's working.

[Ludek]

Curious, let's continue the ticket(s) please..

[dypsis]

Curious, let's continue the ticket(s) please..

I replied to the ticket.

[dypsis]

Thanks for that, @PetrCBR.
I seems like you nailed it. It's been working well. I've opened and closed MM about 10 times without any issues.

Well done.

It'd be interesting to know if the fix works for @FlexFlexerson too.

[FlexFlexerson]

Thanks for that, @PetrCBR.
I seems like you nailed it. It's been working well. I've opened and closed MM about 10 times without any issues.

Well done.

It'd be interesting to know if the fix works for @FlexFlexerson too.

My apologies - I was away my computer for a few days so just catching up now. The special build you shared seems to work. I've opened and closed the app a few times and the problem doesn't seem to reoccur. Thank you!

[rusty]

Thanks! This will be rolling out officially in a new build later today.

-Rusty