Home → Problems →

Crash on file open; crash report attached

• Edit

ryan

13 Dec, 2011 02:17 AM

First off, I love Marked.

However, it has started to always crash when I try to open a file.

I deleted the application, application support files, and preference files, then tried reinstalling from the App Store to no avail. The crash report mentions 'launch path not accessible'. Hopefully, you can track this down quickly.

Appreciate it,
Ryan

• Marked_2011-12-12-210721_Ryans-MacBook-Pro.crash 53.1 KB

1. Support Staff 1 Posted by Brett on 13 Dec, 2011 02:38 AM

   

   My best first guess is that a crash may have happened, the file was moved and then Lion tries to restore the window of the missing file when Mark opens, causing another crash. Could you try following the instructions in this article:

   http://osxdaily.com/2011/07/17/delete-specific-application-saved-states-from-mac-os-x-10-7-lion-resume/

   to remove the saved application state and try launching Marked clean?

   Thanks,
   Brett

   • Edit

2. 2 Posted by Ryan Gomba on 13 Dec, 2011 02:43 AM

   

   Thanks for the quick reply.

   Unfortunately, Marked doesn't have a saved application state in the list.

   Ryan

   • Edit

3. Support Staff 3 Posted by Brett on 13 Dec, 2011 03:08 AM

   

   Is there a com.brettterpstra.marky.savedState ? Due to a last-minute name change before the initial launch, Marked's identifiers show up as "marky." Just checking, if that's not the case, I'll see what else I can come up with.

   • Edit

4. 4 Posted by Ryan Gomba on 13 Dec, 2011 03:09 AM

   

   Nope, that doesn't exist either :)

   Ryan

   • Edit

5. Support Staff 5 Posted by Brett on 13 Dec, 2011 03:21 AM

   

   ok, it looks like one of the scripts Marked uses might be erroring out. Do you have a custom processor installed?

   If not, do you know if anything has altered the location of /usr/bin/ruby?

   • Edit

6. 6 Posted by Ryan Gomba on 13 Dec, 2011 03:38 AM

   

   Aha, I develop with multiple versions of ruby so I use rvm.

   /usr/bin/ruby was pointing to /System/Library/Frameworks/Ruby.framework/Versions/Current (1.8), which actually doesn't exist.

   This fixed the issue:

   mv /usr/bin/ruby /usr/bin/ruby-old
   sudo ln -s ~/.rvm/rubies/ruby-1.9.3-p0/bin/ruby /usr/bin/ruby

   Thanks for your help,
   Ryan

   • Edit

7. Support Staff 7 Posted by Brett on 13 Dec, 2011 03:44 AM

   

   Good deal. I need to shell out to Ruby for some string processing that doesn't work well in Objective-C, so as a consequence I have to rely on the Ruby processor being in the right place. Fortunately, most people who know enough to move it also know how to fix it :).

   Thanks,
   Brett

   • Edit

8. 8 Posted by keithbsmiley on 10 Nov, 2012 06:13 PM

   

   I seem to be having this same issue Brett. My /usr/bin/ruby is already symlinked to the latest version of ruby via RVM. Even when I wipe out all preferences, application support files, and the saved state it launches just fine but crashes on any file I throw at it with the same launch path not accessible error that Ryan cited. Any ideas?

   • markedcrash.txt 43.8 KB
   • markedcrash2.txt 54.3 KB
   • Edit

9. 9 Posted by keithbsmiley on 10 Nov, 2012 06:30 PM

   

   I was actually able to fix this issue by remaking the ruby symlink.. Doesn't make any sense but hey it works.

   which ruby | pbcopy; sudo rm /usr/bin/ruby; sudo ln -s `pbpaste` /usr/bin/ruby
   

   That does it all in one command when using RVM

   • Edit

10. Support Staff 10 Posted by Brett on 10 Nov, 2012 06:59 PM

    

    Thanks for the snippet. Not sure why that would happen, but glad you
    got it sorted.

    - Brett

    • Edit