Simplenote crashed on Sequoia 15.3.1.
-
Simplenote crashed on Sequoia 15.3.1. Perplexity analysis below:
The crash report indicates that the application Simplenote (version 2.21) crashed due to an uncaught exception on the main thread. The relevant details from the crash report are as follows:Key Details
- Exception Type:
EXC_CRASH (SIGABRT)
This indicates that the application explicitly calledabort(), likely in response to a critical error. - Termination Reason:
Namespace SIGNAL, Code 6 Abort trap: 6
This is consistent with a forced termination caused by an unhandled exception. - Application-Specific Information:
The log mentionsabort() called, which is typically triggered when a fatal error occurs that the application cannot recover from. - Last Exception Backtrace:
The backtrace shows that the crash occurred due to an issue with string handling in the-[__NSCFString characterAtIndex:]method. Specifically, this may have been caused by attempting to access an index that is out of bounds or invalid for the string.
Likely Cause
The crash appears to be related to text layout or string manipulation in Simplenote. The following clues support this:
- Text Layout Manager Involvement:
The stack trace includes calls to methods like-[NSLayoutManager invalidateDisplayForCharacterRange:]and-[NSTextCheckingController handleTextCheckingResults:]. These are used for managing text rendering and annotations. - Invalid String Access:
The method-[__NSCFString characterAtIndex:]suggests that an invalid index was accessed in a string, possibly due to corrupted or unexpected data being passed to the text layout system. - Main Thread Crash:
Since this occurred on the main thread, it is likely tied to user interactions with the text editor or rendering updates triggered by user input or background processes.
Recommendations
- Check String Operations:
Simplenote developers should review any code involving string indexing, especially in text rendering or annotation features, to ensure proper bounds checking. - Error Handling Improvements:
Implement safeguards against invalid data being passed into text-processing methods, particularly when interacting with user-generated content or external data sources. - Update Dependencies:
If Simplenote relies on third-party libraries (e.g., Simperium_OSX), ensure they are up-to-date and compatible with macOS 15.3.1. - Test Edge Cases:
Test scenarios involving long strings, special characters, or unusual user inputs that might trigger issues in text handling.
This crash is most likely a software bug within Simplenote’s handling of text data and should be reported to its developers for further investigation and resolution.Citations:
Answer from Perplexity: pplx.ai/share
- Exception Type:
-
I can 100% crash Simplenote on macOS sequoia with exactly on of my very generic notes.
Below is text of the note. It’s fine on iOS and web but 100% crash on Sequoia, even when I copy/paste from web into Simplenote.sequoia.=========
AAFP CME Requirements
Active and Supporting (fp) members must submit at least 150 hours of credit every three years. I’m ‘retired’ so don’t need to.
- at least 75 Prescribed
— teaching med students/residents
— study materials - at least 25 group learning, usually ama categ 1 non aafp
- up to 25 “enrichment”: very broadly defineb
The 150 hours must include at least 75 Prescribed hours and 25 hours from group learning activities.
Enrichment is any activity, including journal reading, that’s not Prescribed or Category 1. Max 25 enrichment hours/cycle.
AMA Category One is “Elective” credit. May 75 hours/cycle.
For notes on Board and MN – https://docs.google.com/document/d/1Gw3FRR0aP9J9pkuRgKjfh8wLd-mqxCLoIGhHZpti7uc/edit?usp=sharing
- at least 75 Prescribed
-
@jfaughnan Thanks for your report.
To confirm, have you also tried to upgrade to Sequoia 15.3.2 and still observe the same crash?
We’re also working a new version that hopefully address the crash issue you had.
-
-
Thanks for confirming, @jfaughnan! I just tested on Sequoia 15.3.2 and Simplenote 2.21 with the note contents you shared above. So far, however, I haven’t been successful in replicating the crash.
Can you let us know of any other steps you are taking before the crash occurs?
If you haven’t already, can you also see if uninstalling and reinstalling the app solves your issue?