I do. I'll have to request permission from the customer though to share it - who will potentially be looking at the file? (Just so I can share names and background with the customer to put him at ease).
- Deon -----Original Message----- From: sqlite-users [mailto:[email protected]] On Behalf Of Jens Alfke Sent: Wednesday, February 21, 2018 9:19 AM To: SQLite mailing list <[email protected]> Subject: Re: [sqlite] iOS Watchdog and database corruption > On Feb 21, 2018, at 7:45 AM, Simon Slavin <[email protected]> wrote: > > My concern was that it's abnormal for "sqlite3LeaveMutexAndCloseZombie" to > take five seconds to execute. As of a few weeks ago, I know all about this function ;-) It's called when the last statement is closed on a "zombie" database connection that's already had sqlite3_close_v2 called on it; it performs the actual close that was deferred. It's taking a long time because it's calling sqlite3WalCheckpoint. But it is scary that the database file got corrupted. Deon, do you still have the corrupted file(s) available for forensics? —Jens _______________________________________________ sqlite-users mailing list [email protected] https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmailinglists.sqlite.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsqlite-users&data=02%7C01%7C%7C257363c1f5294b83d4c408d5794f3e3c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636548303605879185&sdata=91ZUzky2NXRMbmdZ70MnTnW%2FT4crgDMfNTwTXPiDsCg%3D&reserved=0 _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
