[KevinH]

I really find that very hard to accept. Cache files are removed upon exit and never reused, and corruption of the ini may cause segfaults but shouldn't change documents head elements consistently. Also the main Sigil binary is code signed and the signature includes checksums for key pieces. If corruption happens, the signature test will fail and the OS will abort it.

So something else strange is going on. Sounds like memory issues coupled with alsr/pie security moving the binary load location into and out of bad memory banks when loaded to someplace else.

Either way, glad you have it working again. If it happens again, you may want to check the integrity of both your memory and your hd/ssd/storage device.