Under review

New version crashes on my mac

x3blis 5 years ago updated by Alexander Blach (Developer) 5 years ago 2

Mac mini Server (Mid 2011) 

On start up program i get crash mistake:

Process: Textastic [1141]
Path: /Applications/Textastic.app/Contents/MacOS/Textastic
Identifier: com.textasticapp.textastic-mac
Version: 4.0 (34)
App Item ID: 572491815
App External ID: 829064855
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Textastic [1141]
User ID: 501

Date/Time: 2019-01-15 09:42:22.192 +0300
OS Version: Mac OS X 10.13.6 (17G4015)
Report Version: 12
Anonymous UUID: 10C1D385-D236-AC1F-F09C-D0625E91EF69

Sleep/Wake UUID: F5D79C21-D795-425B-8C11-8DC60E9C35BB

Time Awake Since Boot: 13000 seconds
Time Since Wake: 1100 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000018

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [0]

VM Regions Near 0x18:
__TEXT 0000000102c07000-0000000102ebd000 [ 2776K] r-x/rwx SM=COW ~? [/Applications/Textastic.app/Contents/MacOS/Textastic]

Application Specific Information:
objc_msgSend() selector name: release

Solved. Removed Texstastic with CleanMyMac and reinstalled program. Al work ok.

Under review

I'm aware of a crash that happens to some users when restoring the application state on macOS 10.13.6. It does not seem to happen on 10.14 Mojave.

Please try the following to fix the problem:

  • Go to Finder
  • Select Go -> Go to Folder…
  • Enter "~/Library/Containers/com.textasticapp.textastic-mac/Data/Library/" and press Go
  • Delete the folder "Saved Application State"
  • Try to launch Textastic

If that doesn't help, you can also try to delete the folder "~/Library/Containers/com.textasticapp.textastic-mac" which will remove all preferences, saved application state, custom syntax definitions, themes and templates. It won't delete your documents.

I'm really sorry for the inconvenience. I'm still trying to figure out what exactly is causing the crash.