Friday the 13th > Trying to delete BLOB > OutOfMemorError > DB corrupted > Recover tools says "File corrupted in chunk 310, expected page length 4..3072, got 140732533"

[rho]

Hi 

Using 1.4.199. New database just two weeks old, running in Jetty web application. I was the only user working on it, deleting a few dozen image blobs one by one via the webapp.

My application apparently has a memory leak, so when I tried to delete another image, an OutOfMemoryError happened (actually this was already the 2nd out-of-memory, but in the previous instance the db did not get corrupted, and I was able to just reboot the server).

I am pretty sure that the only write statement in progress at that moment could have been "DELETE FROM my_attachments_table WHERE id=?". Inside a transaction, with LOCK_MODE=1.

Now the database is corrupted and the Recover tool also throws an exception.

Am I already out of options? :(

(frustration rant of the moment: H2 database corruption just happens way too often in my experience, which is a real pity, because I love H2)

Reto