On 7 Feb 2018, at 3:16pm, Deon Brewis <de...@outlook.com> wrote: > So this looks more like something is overwriting the memory of Page1 before > SQLITE writes it back to disk.
That is almost always what people eventually admit to after reporting a problem like this. Some part of their code is stomping on memory or a file handle which SQLite thought it had exclusive rights to. Some of them discover it using a runtime profiler tool which looks for use of released memory or double-release of file handles, but I don't know enough about Windows to suggest anything. Simon. _______________________________________________ sqlite-users mailing list email@example.com http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users