[color=#4040BF][b]UPDATE[/b]: I killed the MM5 process, re-ran the MM5 maintenance, closed MM5 and copied/renamed the DB back to MM4 and I think I'm in business.

The file size is back down to 641MB, but need to have MM4 do search indexing (because nothing comes up on a search)[/color]

[color=#4040BF]Thanks, Peke.

It seems my database even killed MM5, it's currently a white window not responding to clicks (but still minimizes and restores, so odd).

Steps taken (from gathered research):[/color]

[list][*] install clean portable version of MM5
[*] start MM5 once to fully create its INI file
[*] cancel to 1st time wizard and close MM5
[*] update MM5 ini file in portable:
[/list]

[quote][Options]
ForceMM4Compatibility=1
[Portable]
IsPortable=1
[/quote]

[list][*] copy MM4 MM.db to MM5 portable directory and rename db to MM5.db
[*] start MM5
[color=#990000]>>> NOTE: even with "ForceMM4Compatibility" set MM5 still upgraded the database![/color]
[*] Manage Database, run with:
[list][*]rebuild database checked
[*]FTS rebuild checked[/list]
[color=#339900]>>> My MM5 session is hung-up HERE[/color]
[*] close MM5
[*] copy MM5.db to MM4 portable and rename db to MM.db
[*] open MM4 portable (and hope for the best)[/list]

[color=#4040BF]The Portable directory currently has:
an MM5.DB-journal file that has not been updated in over an hour 10MB
an MM5.db file that also has not been updated in over an hour 21GB

So, no way to have MM4 just rebuild the database (without losing play counts, etc.)? Or do you think something was funky when it was only 900MB and the re-index made it grow appropriately to 25GB? Curious.[/color]

Hi,
My best suggestion would be to install MM5 portable -> Copy MM.DB -> MM5.DB in Portable folder and after start do Rebuild library. As fro MM4, I guess the best approach would be to revert to week old DB and se eif it will happen again along with full text search reindex.

This is the first time I have ever heard such case.

[color=#4040BF]Okay, thoroughly confused now. Started with a 900MB database and thought I needed an Optimize (Complete) run since MM was a bit sluggish on startup.

I watched it for 4 hours as the DB grew in size, eventually growing to 24GB! :o

I killed the MM process and performed a SQLite Vacuum command which only dropped it to 22GB.

Has anyone experienced this and/or have a potential solution other than (1) reverting to a backup from 2wks ago; or (2) starting over with a clean database?[/color]