5 ms·
The opaqueness is definitely a problem. My iMessage database has a corrupted spot somewhere in the message history; if I accidentally make the Messages app read
by Nextgrid 3y ago
The opaqueness is definitely a problem. My iMessage database has a corrupted spot somewhere in the message history; if I accidentally make the Messages app read that spot (via searching or scrolling back through old conversations) it'll silently start maxing out the CPU and burning energy for no reason. There is no error message, nothing obviously wrong-looking, and as far as I know everything works.
- farconics 3y agoSounds like a nightmare. Do you know what could have caused the database corruption?
- Nextgrid 3y agoCouple years of macOS/iOS reinstalls along with the typical shittiness of iCloud and the iMessage clients. I would be more surprised if it wasn't corrupt.
- o-o- 3y agoOh, so that's what's happening? You made me realise I have the same exact issue!
- Nextgrid 3y agoWell I can't for sure prove it's indeed DB corruption, but I don't have many other theories. It's unlikely to be a "static" bug affecting everyone because it would've been caught in QA and/or user reports and fixed already (this is not a new issue, been happening for a year at least). Therefore my hypothesis is that it's dependent on corrupt persistent data that a relative minority of users have which is not easy for Apple to detect/replicate.
- css 3y agoHey, this sounds like an interesting problem. I am always looking for edge cases to test, if you have time would you mind checking if https://github.com/ReagentX/imessage-exporter https://github.com/ReagentX/imessage-exporter works for you and if it crashes in that spot?
- the_gastropod 3y agoHoly crap. I've been looking for ways to archive my imessages somehow. imessage-exporter looks like exactly what I wanted. What a cool project!
- css 3y agoCheers! It was fun to build.