[2178] - Out of Memory (7,7)

[MMuser2011]

If I try to "Manage Database -> Optimize database" I get this error during VACUUM:



Forgot to say:
PC has 32GB RAM

[Ludek]

How large is your database (MM.DB) file?

Would you mind zip (compress) it and share with us for analyzing? e.g. zip (compress) your MM.DB file and upload it to a free file hosting service (DropBox, RapidShare, FileDropper, MediaFire, ...) and share the link to the file with us (e.g. send me private message with the link)

[MMuser2011]

Actually my Win10 Explorer says for the MM4-DB:
7'358'137 KB

I'm still waiting (since more then 2 hours) that MM5 is rebuilding this DB completely

You get a PM as soon as the MM4-DB (the one I copied and try to use for the portable MM5) is compressed and ready to DL for you.
[Done...]

I assume that you delete this DB after your analysis?

[Ludek]

Thank you, I've received it and yes, I am going to delete it after the analysis.

[MMuser2011]

Ok, thanks.

MM5 has finished rebuilding this DB.
The size of the DB was reduced to 4'728'904 MB.

[Ludek]

hmm, 2.2 million of tracks, really a large collection
I guess that the largest that I've ever seen

I will see what can I do, but I guess we will need to create 64-bit version of MM soon, to be able to go after the 4GB RAM limit for such a large collections.

MM5 has finished rebuilding this DB.
The size of the DB was reduced to 4'728'904 MB.

Should I understand it that you no longer have the "Out of memory" issue?

[MMuser2011]

Should I understand it that you no longer have the "Out of memory" issue?

I can't tell you that yet. It just finished some minutes before my post.

I try to do the steps with this freshly rebuilded MM5-DB again and let you know the result very soon.

[MMuser2011]

.. really a large collection I guess that the largest that I've ever seen

That is one of the reasons for my other thread.
Every little bit of optimization results in fewer minutes of waiting for me

[MMuser2011]

Should I understand it that you no longer have the "Out of memory" issue?

Unfortunately not, no.

I press "Optimize database" and then I see the faded background and a process bar.
This process bar fills from left to right.
At the VACUUM status (approx 90% of the process bar) the screen turns to completely white - without anything visible, no resize icons, no hourglass, nothing, and I can't reach the MM5 main window anymore. I can switch to other running programs like the taskmanager.

The taskmanager shows CPU 0% for "MediaMonkey (32bit)" and 0% for "MediaMonkey5". I don't know if the VACUUM is still running or if the process is halted. How long should this VACUUM "normally" need?

The last few lines from DebugView:

Code: Select all

00003173	91.56558990	[14220] MM5 [8288](R) DB lock took 10813 ms : REINDEX IUNICODE	
00003174	91.56573486	[14220] MM5 [8288](R) DB exec SQL: VACUUM	
00003175	100.91764069	[14220] MM5 [1996](R) Still waiting for event (callstacks) :	
00003176	100.91768646	[14220] MM5 [1996](R) Wait for event ID :3, delay :10000, callstack :	
00003177	104.92025757	[14220] MM5 [8288](R) SQLite error - Error executing SQL statement "VACUUM" : out of memory (7, 7)	
00003178	104.92102051	[14220] MM5 [8288](R) DB lock took 13359 ms : VACUUM	
00003179	104.92108917	[14220] MM5 [8288](R) SQL ERROR: Error executing SQL statement "VACUUM" : out of memory (7, 7), query: Es gab ein Problem beim Abfragen der Datenbank: 	
00003180	104.92108917	[14220]  	
00003181	104.92118835	[14220] MM5 [8288](R) TSharedWindow created.	
00003182	104.92658997	[4508] MM5 [8824](B) Retrieving file file:///dialogs/dlgMessage.html	
00003183	104.92677307	[4508] MM5 [8824](B) buildPathFromUrl from file:///dialogs/dlgMessage.html to dialogs\dlgMessage.html	

....

00003200	104.96419525	[14220] MM5 [1856](R) load event call 6	
00003201	110.93266296	[14220] MM5 [1996](R) Still waiting for event (callstacks) :	
00003202	110.93273926	[14220] MM5 [1996](R) Wait for event ID :3, delay :10000, callstack :	
00003203	120.94961548	[14220] MM5 [1996](R) Still waiting for event (callstacks) :	
00003204	120.94966888	[14220] MM5 [1996](R) Wait for event ID :3, delay :10000, callstack :	
00003205	130.96453857	[14220] MM5 [1996](R) Still waiting for event (callstacks) :	
00003206	130.96459961	[14220] MM5 [1996](R) Wait for event ID :3, delay :10000, callstack :	
00003207	132.24302673	[14220] 	
00003208	132.24302673	[14220] <--- Last few GCs --->	
00003209	132.24302673	[14220] 	
00003210	132.24302673	[14220] [14220:07949450]   108653 ms: Mark-sweep 20.0 (26.3) -> 19.6 (25.8) MB, 19.4 / 4.6 ms  (average mu = 0.999, current mu = 1.000) low memory notification GC in old space requested	
00003211	132.24302673	[14220] [14220:07949450]   108670 ms: Mark-sweep 19.6 (25.8) -> 19.6 (25.8) MB, 16.8 / 4.0 ms  (average mu = 0.998, current mu = 0.001) low memory notification GC in old space requested	
00003212	132.24302673	[14220] 	
00003213	132.24307251	[14220] 	
00003214	132.24307251	[14220] <--- JS stacktrace --->	
00003215	132.24307251	[14220] 	
00003216	132.24736023	[14220] MM5 [1856](R) Exception!! - External exception E0000008.	
00003217	132.49645996	[14220] Dump(String): "PanicModeOn: FATAL PROBLEM"	

[PetrCBR]

White screen is signal for engine process crashed for some reason (in your case it's probably on Out Of Memory).

[Ludek]

FYI: The VACUUM "out of memory" exception will be fixed in the next build (2179)

I replicated the issue on your database.

[MMuser2011]

FYI: The VACUUM "out of memory" exception will be fixed in the next build (2179)

Thank you for the feedback, Ludek!
Could this problem also occur in MM4 or is this only MM5 related?