MM freezes on startup

[kjaem24]

I have been using MM for a long time and have never had this problem until today. Using the current beta build .1250, MM freezes at the splash screen and the computer runs at 100% for several minutes. I tried uninstalling and reinstalling to no avail. I also installed the previous builds which had worked fine and it didn't work. I renamed the iphone.dll to iphone dll.off and that didn't work either. It freezes and will not shutdown, I have to ctrl+alt+del to manually shut it down.

[Suburbancowboy]

Did you recently upgrade to itunes 8.2?
It is a known issue. The newfangled version of iTunes is causing MM to crash when the phone is plugged in. Is it not crashing when the phone is not connected to the computer?

http://www.mediamonkey.com/forum/viewto ... hilit=beta

[Guest]

Nope. I don't even have itunes or quicktime installed. I just uninstalled MM and dumped the folder, reinstalled onto my G drive and it works fine now. I am not sure at what cost. I did a virus scan and got nothing. Hopefully the problem doesn't carry over onto my external G drive.

[julial49]

I have had a similiar problems for a few versions now. I have to start MM at least three times (and cancel it via task manager twice) before it is ready to use.

I do not have a phone or any other mp3 players connected at the moment of startup.
iTunes is installed on my computer (XP)

MM library is located on an external hard drive.

[Lowlander]

@julial49
What version of iTunes and MediaMonkey do you have installed. Please provide more details as otherwise it's hard to determine what might be causing this.

[julial49]

lowlander, I use the most current version of MM ( 3.1.0.1256) and iTunes 8.1.1.10. I updated iTunes to 8.2 and I'm still having the freeze problem.

Here's how it usually goes:
1. click desktop link to start MM
2. cpu load goes up and after about 20-25 secs goes down to almost zero and MM is not responding
3. kill process and repeat steps 1 and 2 (once)
4. start MM again and this time the cpu load does not go down to zero but eventually MM starts

This is independent of how many songs are in the Now Playing list. I know that MM started for real when the mini player shows up in the task bar (and not just the symbol in the system tray). That is a very weird problem I think.

[Lowlander]

Try creating a debug log as described in the Bug Report forum.

[julial49]

OK, installed the debug version and sure enough on startup some error messages popped up (and up and up and up and up - you get the picture). It looks as though the iPhone integration is to blame. Here are the last few lines of the debug log:

00000364 32.84018326 [14108] 8488 DB lock successful.
00000365 32.84049225 [14108] 8488 DB lock finished, took 713620.
00000366 32.84058380 [14108] 8488 DB exec SQL: DELETE FROM SkipInDuplFind WHERE NOT EXISTS (SELECT 1 FROM Songs WHERE SkipInDuplFind.SkipId=Songs.Id)
00000367 32.84063721 [14108] 8488 DB lock successful.
00000368 32.84097672 [14108] 8488 DB lock finished, took 860948.
00000369 32.84764862 [14108] 8488 DB open SQL: SELECT COUNT(*)-1 FROM TmpADFCreateInfo WHERE UsedWhere IN (1,3)
00000370 32.84815598 [14108] 8488 DB lock finished, took 1422240.
00000371 32.85094833 [14108] 8488 DB open SQL: SELECT COUNT(*)-1 FROM TmpADFCreateInfo WHERE UsedWhere IN (2,3)
00000372 32.85145187 [14108] 8488 DB lock finished, took 1214848.
00000373 33.41073608 [14108] 8488 DB open SQL: SELECT Date(MIN(DateAdded+2415018.5)) FROM Songs WHERE Cast(julianday('now','localtime')-DateAdded-2415018.5 as integer) < 10000
00000374 43.33859634 [14108] WMDM: Notifications ok.
00000375 43.33963013 [14108] WMDM: Looking for device changes...
00000376 43.34111786 [14108] WMDM: Finished action id: 0
00000377 44.75414276 [14108] iPhone: LoadLibrary() finished
00000378 44.75428772 [14108] iPhone: iTunesMobileDeviceSupport loaded
00000379 44.76452637 [14108] iPhone: AMSInitialize : 0
00000380 44.97541046 [14108] iPhone: AMDeviceNotificationSubscribe : 0

[Lowlander]

Did you send the full log to support?

[julial49]

On second startup there were fewer error messages. The debug log looked like this:

00000364 7.66303682 [12660] 904 DB lock successful.
00000365 7.66355658 [12660] 904 DB lock finished, took 1294672.
00000366 7.66371059 [12660] 904 DB exec SQL: DELETE FROM SkipInDuplFind WHERE NOT EXISTS (SELECT 1 FROM Songs WHERE SkipInDuplFind.SkipId=Songs.Id)
00000367 7.66376448 [12660] 904 DB lock successful.
00000368 7.66427135 [12660] 904 DB lock finished, took 1317572.
00000369 7.67035580 [12660] 904 DB open SQL: SELECT COUNT(*)-1 FROM TmpADFCreateInfo WHERE UsedWhere IN (1,3)
00000370 7.67077303 [12660] 904 DB lock finished, took 1071132.
00000371 7.67524624 [12660] 904 DB open SQL: SELECT COUNT(*)-1 FROM TmpADFCreateInfo WHERE UsedWhere IN (2,3)
00000372 7.67557192 [12660] 904 DB lock finished, took 1005824.
00000373 7.72844934 [12660] 904 DB open SQL: SELECT Date(MIN(DateAdded+2415018.5)) FROM Songs WHERE Cast(julianday('now','localtime')-DateAdded-2415018.5 as integer) < 10000
00000374 8.52852917 [12660] iPhone: LoadLibrary() finished
00000375 8.52862167 [12660] iPhone: iTunesMobileDeviceSupport loaded
00000376 8.52941322 [12660] iPhone: AMSInitialize : 0
00000377 8.56611061 [12660] iPhone: AMDeviceNotificationSubscribe : 0
00000378 12.87919521 [12660] WMDM: Notifications ok.
00000379 12.87924480 [12660] WMDM: Looking for device changes...
00000380 12.87933826 [12660] WMDM: Finished action id: 0

and then the third time after line 380 there are lots and lots more things happening. It just does. Let me know it you need the complete debug log. This happens EVERY time I start MM.

[julial49]

Did you send the full log to support?

You mean via the error message? Or via email?

[Lowlander]

Via email as described in the bug report topic.

[julial49]

With the 3.1.1 RC (released today) the problem still persists. I actually think the number of error messages increased with the new release.
I sent almost all of them with the "Send report" function. Hope it helps because I really don't want to start MM anymore since it takes about two minutes and a lot of clicking till it finally is ready. And while MM starts up Firefox and Thunderbird are frozen too.

[Peke]

Last few versions could not make things worse as they only include Amazon tagging fix and no other bug fixes.

[julial49]

Last few versions could not make things worse as they only include Amazon tagging fix and no other bug fixes.

Ok, then it just seemed more often because I send the error reports. Any chance this issue is fixable and soon?
These days I listen with Spotify more and more often and only start MM if it is really necessary which is a shame (I have a lifetime license).