Bug: Error then froze while SENT TO

[dtsig]

Current MM beta (I would look but it is frozen again). 4.1.0.1623
When trying to 'Send To' a playlist to my phone (mma 1.0.1.0098) I got a really log error message with the heading error (really )

In then 'problem' box, which you can't copy/paste, there is a long list of problems. See image ..



For some reason it thought it would 'delete' things. Not sure why as i asked it to SENT TO.

I wanted to save the list so i pressed 'Save as Playlist' but this caused the state you see now. FOZEN. Tried to close the window but that wouldn't work. Had to task manager it.

[Lowlander]

You database is on the fritz: http://www.mediamonkey.com/support/inde ... ticleid=78

[dtsig]

That is sad. I have had no problems with MM for a long time. This beta and MMA beta seem very buggy.

Guess will go back to the regular release and just use the beta for a few minutes a day.

Thanks for the link

[Ludek]

There is nothing bad with your MMW DB (MM.DB)

This kind of errors only say that MMW downloaded DB from MMA and on the attempt to write to MMA's DB during sync there was a problem (the DB was probably downloaded only partially from the device or MMA's DB is somehow corrupted).

I guess you synced via USB in MTP mode?
Do you have latest version of MMA?
Does this happen on every attempt to sync with MMA?


Could you send me debug log?

[dtsig]

There is nothing bad with your MMW DB (MM.DB)

This kind of errors only say that MMW downloaded DB from MMA and on the attempt to write to MMA's DB during sync there was a problem (the DB was probably downloaded only partially from the device or MMA's DB is somehow corrupted).

I guess you synced via USB in MTP mode?
Do you have latest version of MMA?
Does this happen on every attempt to sync with MMA?


Could you send me debug log?

Ludek, That is great news ... would have been sad if I had to redone my primary MM.

Yes, I synced via USB. MTP mode is the standard Android share mode for access .. yes?
Yes, using MMA .0098 and MM .1623 (i think these are still most current)

I have started a sync right now (playlist to existing samsung songs) and if this happens again I will send a log. Is the log to come from MMA or MM? My *guess* is MM but want to be sure.

Either way I will post the results.

Thanks for the follow up .. hate to be such a pest

[Ludek]

Attach MMW log (generated using DbgView app) once the issue re-appears, be sure that DbgView is run prior to MMW, you can use Ctrl+X in DbgView to clear the log it prior to sync in order to minimize log size.

Thank you.

[dtsig]

First, i didn't see your reply in time but now have downloaded the dbgview for future use.

The Send To only lasted for about 45 minutes which is a really short time as last time it was a couple hours before it froze with error msg.

Samsung/music shows 4037 songs
Playlist/Samsung/music shows 4081

Before this last Send To there were approx 3500 songs (don't remember exact number)

So it seems that it didn't bring across all songs again but no error messages were noted.

Would you like me to do the Sent To again with dbgview running?

EDITED: I forgot to mention that I now have duplicates again on the Samsung. It must be only the DB because Winamp does not show duplicates.

Thanks again

[Ludek]

I think you don't need "Send to device" all the tracks, it should be reproducable also with one or two tracks, because MMW downloads MMA's DB just when sync starts and uploads the DB back for MMA when sync ends.

And yes, the duplicates are consequences of the errors.

In past I had similar problems, because Android content is not refreshed in case of MTP, but we resolved it.
If MMW downloads a malformed DB then it tells MMA that MMA should create safe copy of the DB and MMW downloads the safe copy then.

It has always worked on my phone (Samsung Galaxy Nexus), but it seems that it doesn't always work with your S3, the debug log should tell me why.

I will laso re-test this with the latest build to ensure there is no regresion in this workflow between MMW and MMA.

[Ludek]

BTW:

I've gone through this and I found one scenario in which this could happen.

See details here:
http://www.ventismedia.com/mantis/view.php?id=10470

So maybe until 10470 is fixed, you don't need to generate log.

[dtsig]

Ludek, thanks again for the quick follow-up

i looked at the mantis issue and I have been doing no editing on MMA but .. I will wait until the next update of MMA/MM to recheck this. It could be related. I will also keep a look at 10470.

Thanks again

[Ludek]

OK, editing is not necessary, because MMA can change its DB also just by browsing etc. and then MMW doesn't see actual content over MTP and can download a malformed DB then.

I also reported the issue with duplicate tracks:
http://www.ventismedia.com/mantis/view.php?id=10471
where I found also another steps to repro than just failed sync mentioned by you.

[dtsig]

Way cool ... 2 birds with one stone.

Have a great (and productive?) weekend.

[Ludek]

I have just reproduced the "malformed DB" issue, it will be fixed as
http://www.ventismedia.com/mantis/view.php?id=10487