MM4 Starts and then freezes

[marphod]

I've tried installing MM4 as a portable installation and as a standard install. The behavior happens on either. I've tried uninstalling and re-installing, and this behavior starts happening after a few executions, and once it happens, it happens every time.

On execution of media monkey, regardless of the /nosplash flag, the application starts, loads my library and places me in the same place in the organization tree as when I last quit, and then hangs. I've let it sit for over an hour, and its memory footprint doesn't change and it barely registers any CPU usage when i check performance counters, so it does seem to be truly stuck.

The only thing I can think that might cause the crash is that I'm removing duplicates and correcting tagged information. Is that causing something to fall out of sync?

(Windows xp 64bit SP 2, 4G ram -- not that MM goes over 64M, Inter Core 2 Quad Q9550 -- not that my CPU usage goes over 10%, around 6k media files, mostly audio and most of those are MP3s, a couple-dozen podcasts and a handful of audio books)

[Lowlander]

Try 4.0.3.1473: viewtopic.php?p=331246#p331246

[marphod]

No luck.

Actually, the behavior has changed. Rather than starting, displaying the main window and hanging, it just hangs after the splash screen and never draws the main window.

[windcrest77]

This happened consistently to me too (MM4 Gold) but I have a "fix" for it.

The problem has to do with MM4 trying to populate all 200,000 tracks to the grid at program launch. It consistently stops and hangs at about 35,000 tracks at start up then you have to use Task Manager to kill it. The way I "fixed" this is to simply make sure that the "Now Playing" tree node is always the selected node whenever I shut down MM. Then when it starts again there is nothing to populate the grid with and the MM4 starts up fast. After starting MM4 with "Now Playing" tree node selected instead ofthe "Library" node everything is fine, at that point I can click the main library node and all 200,000 tracks populate in about 15 seconds. The problem only happens at start up time AND there are a lot of tracks loading into what I like to call, "the big ass grid".

I really wish MM4 would "virtualize" the grid at some point. There really is no reason the grid HAS to have all 200,000 tracks in it, the grid only needs to contain the 50 or so tracks that are actually in view. The other 185,985 tracks (or remainder of the query tracks) should just be in a data table in memory. Grids should dispose and create rows as the user scrolls so its just a viewportal with the in-memory table doing all the sorting, getting updates, etc.

This huge grid is the source of 99% of MM4's performance issues. Like the imfamous library scan with 200,000 tracks in the grid that takes over 24 hours vs the same scan done with an empty grid that takes 20 minutes.

Not being negative, I hope I'm being constructive, MM4 is still the best library manager out there.

[Lowlander]

Rename d_iphone.dll to d_iphone.dll.off in the Program Files\MediaMonkey\Plugins folder: http://www.mediamonkey.com/support/inde ... ticleid=33

[marphod]

Well, bizarre.

While changing the .dll's name didn't work when I tried it on a normal 4.0.1 install, it did work on 4.0.3 portable.

(For what it is worth, upgrading Quicktime is a ROYAL PAIN IN THE ASS. I'm on, as I mentioned, XP 64 bit, which is not supported by Apple. You can hack together a working install, but it is far from perfect.)


(I don't have that many tracks -- I'm around 10k, over an order of magnitude smaller than the 200k problem area)

[Lowlander]

That may be where your problem lies. If you hacked together QuickTime MediaMonkey may be expecting components that aren't on your system. Renaming d_iphone.dll would solve the problem in that case.