"BUG IN CLIENT OF libsqlite3.dylib" when closing autosaved document #2
Comments
evanmiller
pushed a commit
that referenced
this issue
Jun 8, 2019
WIP Execute completion handlers on main queue
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Not 100% reproducible but when closing a document with autosavingInPlace turned on, I often see:
[logging] BUG IN CLIENT OF libsqlite3.dylib: database integrity compromised by API violation: vnode unlinked while in use: /XXX/Autosave Information/XXX/Storage-009.sqlite-shm
[logging] invalidated open fd: 22 (0x11)
[logging] BUG IN CLIENT OF libsqlite3.dylib: database integrity compromised by API violation: vnode unlinked while in use: /XXX/Autosave Information/XXX/Storage-009.sqlite-wal
[logging] invalidated open fd: 21 (0x11)
[logging] BUG IN CLIENT OF libsqlite3.dylib: database integrity compromised by API violation: vnode unlinked while in use: /XXX/Autosave Information/XXX/Storage-009.sqlite
[logging] invalidated open fd: 20 (0x11)
The text was updated successfully, but these errors were encountered: