I'm working on converting browser SQLite usage from regular I/O to mmap. It uses less memory and should be faster. One side effect is that where attempting to do regular I/O on a corrupt filesystem returns errors, you can sometimes mmap successfully but then crash trying to access data in the mapped memory (*).
I'm wondering if there's any way to detect that this may have happened, so that on startup the code can do something more thorough before proceeding. Is anyone out there plugged in to the Chromium state-of-the-art in this area?
Thanks,
scott
(*) This also can happen to any other place we use mmap, of course. In those cases your Chrome probably stopped working at some release and you re-installed or something. In this case, Chrome kept working, just one of your databases didn't, until this change.