Error during player initialization [#8077]

[Guest]

Since the early betas I have been having this problem. I figured it would get resolved eventually, but it hasn't and I have pretty much had it with Mediamonkey.

I get the error "Error during player initialization" when I start mediamonkey. When I click OK, everything starts fine, then in my media tree all "Music" nodes are missing. Only playlists, media servers, my computer, etc... I can still play music via playlists but eventually I get an "Assertion Error".

The ONLY way I have found to get it back is to revert to an old version of my database.

It happens consistently after receiving a cascading error referring to some sort of "Assertion error". I can't quite read the error window because so many pop up so fast. It happens randomly, when organizing tracks, ripping CDs, or even just listening to music and not otherwise interacting with MM.

When this error happens, the "Error during player initialization" always happens on the next startup.

I am now using build 1394 on Windows 7 SP1. This has happened from when I first started using MM 4 betas around January.
It should also be noted I have songs/files in many different languages, including Asian languages.

[Lowlander]

http://www.mediamonkey.com/forum/viewto ... ?f=6&t=341

Have you tried a clean install?

[crazymonkey]

http://www.mediamonkey.com/forum/viewto ... ?f=6&t=341

Have you tried a clean install?

I have, as well as a portable clean install.

And I made a mistake before, it was an "Access Violation ______ in module ______" not an "Assertion Error". It just happened again.

[crazymonkey]

Sorry, I didn't realize I wasn't logged in the first time...

[crazymonkey]

My database was originally a MM3 database. I have tried using many versions of my database, but reverting to a pre-crash database always makes things work perfectly again.

[crazymonkey]

Also, I have a quad core computer, and MM4 sits at 25% processor usage pretty much all of the time. When it crashes, the process continues, and still is 25% even though the window is gone.

[rusty]

Hi Crazy Monkey,

Can you please send a debug log? I would _really_ like to get to the bottom of this.

Thanks.

-Rusty

Edit: I missed your comment where you indicated that you sent a debug log. Do you happen to know the ticket ID ? I can't seem to find it. Thanks.

[crazymonkey]

I also send a crash report thingie (When MM crashed, I sent the thing through the dialog box).

How do I attach a file to this? I don't see any options.

[crazymonkey]

Ah, the "Assertion Error" happens when I try to close Mediamonkey after the stuff that happens above.

[crazymonkey]

I think the ID of that crash log I sent in is:

2.7 ID : 5DA9

(This is for the Assertion Error)

[rusty]

CrazyMonkey,

We received the automatically submitted log, but it didn't give us enough information. Could you post a debug log generated with debugview?

Thanks.

-Rusty

[crazymonkey]

I messaged you with the link to the debugview log already. Didn't you get it?

[crazymonkey]

I have noticed very strange things happening with my tracks in the database.

The song information in Mediamonkey is all mixed up.

Some songs have completely wrong metadata listed in Mediamonkey, though, their ID3 tags seem fine.
In the MM library a song would have the Title, Artist, Album,etc of a completely different song. The filename and the ID3 tags are correct though, so MM is getting it's wires crossed somewhere.

[nynaevelan]

I am also getting this message on my work machine, I upgraded from 1393 to 1397. Here is the log: http://dl.dropbox.com/u/13254132/player ... zation.LOG


Nyn

[Ludek]

I am also getting this message on my work machine, I upgraded from 1393 to 1397. Here is the log: http://dl.dropbox.com/u/13254132/player ... zation.LOG


Nyn

I see in the log that you have some script which creates temp tables like TmpDelSugg2TSC during MM startup, does the problem appear also if you start MM without any scripts?