I'm trying to follow Richard's advise to work around this issue, which is: "Is that database ever used by more than a single process. (Use by multiple threads using separate connections does not count - I mean really used by multiple processes with their own address space.) If not (and I think the answer is "no") then FF could set "PRAGMA locking_mode=EXCLUSIVE" immediately after opening the database and before doing anything else. If that is done, then SQLite will use heap memory for the WAL-index, instead of mmapped shared memory, and this problem will never come up."
However, I'm unable to do so. I'm using multiple threads using separate connections, like mentioned, but when I try to use PRAGMA locking_mode=EXCLUSIVE, the next thread that tries to open a connection will block indefinitely on the open. So how can I go about using PRAGMA locking_mode=EXCLUSIVE while still using multiple threads with connections? -- View this message in context: http://sqlite.1065341.n5.nabble.com/Bug-993556-SQLite-crash-in-walIndexTryHdr-due-to-Windows-EXCEPTION-IN-PAGE-ERROR-exception-tp78695.html Sent from the SQLite mailing list archive at Nabble.com. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users