Hello @aguynamedben - thanks for these additional details. This is a difficult issue to pin down. I posted over to the Signal thread about a tool that will help us determine on the one corrupted database available whether the file has been manipulated externally, or if the data is inconsistent internally. It is our hope this will help narrow things down.
With respect to the possible causes, I don’t think we can completely rule out the issue of linking multiple versions of SQLite, because it appears that electron actually embeds a copy of SQLite itself. We can’t say for certain that this would cause a problem, since technically they should not be opening the same database files, but it’s a consideration.
It would be very helpful to have a stripped-down/minimal application that is setup with SQLCipher that we could run some experimentation with. I’m thinking something along the lines of a simple electron app that just has a button and a text output control, which, when pressed, can execute some SQL on a SQLCipher database. We could expand that on our end to run some various load testing, and/or experiment with killing the app in various states. Unfortunately we’re not particularly experienced with electron tooling and development, so preparing that wouldn’t be a quick and trivial effort for our team. Would you be able to put something like that together and share the code with us? If so, it might help move things along.