Crash with no error causes corrupted file
Status: Beta
Brought to you by:
alphagremlin
Menu
▾
▴
#3 Crash with no error causes corrupted file
NeoJournal crashes with no error whilst saving a journal item, due to attempting to create an impossibly large block of data. The journal datafile ends up partially corrupted as it is in the middle of a write.
Some code changes in Beta 3 will help prevent this, including crashing safely with a sanity check on the amount of data to be saved, and the ability to detect and skip over the corruption caused. Corrupted files will open as read-only, and users should use the "backup" and then "restore" features to rebuild the file.
No idea what the cause is just yet, but I'm looking into it. Hopefully the changes will let me catch the error.
If you encounter this error and wish to recover your Journal, please contact me and I will provide a recovery program.
AlphaGremlin
Logged In: YES
user_id=1662029
Originator: YES
It's just crashed again on me, and now I'm unsure as to what is causing it. I received an OutOfMemory error this time, only this was caused by it attempting to display yet another error!
Has anybody else encountered this problem yet? It's proving rather difficult to track down.
AlphaGremlin
Logged In: YES
user_id=1662029
Originator: YES
I've had a few more people say they've encountered this problem. There are some minor adjustments made in Beta 3 that should prevent it from happening further, but I'm not sure if I'll close this bug just yet...
AlphaGremlin