Home → Problems →

Marked quit unexpectedly

• Edit

cary

08 Jul, 2012 10:30 PM

Marked has been working as expected, but recently I am receiving the "Marked quit unexpectedly." message when trying to open a file.

I've tried different files with the same outcome.

Marked version 1.4 (221) from the Mac App Store.

Any help would be much appreciated.

Thank you,
Cary

1. Support Staff 1 Posted by Brett on 08 Jul, 2012 11:47 PM

   
   1. What kinds of files? Anything other than plain text? It shouldn't crash even then, just curious
   2. Can you open up Console.app in your Applications/Utilities folder and look for a crash report from Marked in the lefthand column? Just attach the most recent one, please.
   • Edit

2. 2 Posted by Cary Landholt on 09 Jul, 2012 12:04 AM

   

   Please find the requested log file attached.

   Thank you

   • Marked_2012-07-08-185900_Cary-Landholts-Mac-Pro.crash 44.8 KB
   • Edit

3. 3 Posted by Cary Landholt on 09 Jul, 2012 12:07 AM

   

   oh - and this happens regardless of the file type.
   Also, I'm an admin.

   • Edit

4. Support Staff 4 Posted by Brett on 09 Jul, 2012 12:24 AM

   

   DId you add a custom processor or enable that option at all?

   • Edit

5. 5 Posted by Cary Landholt on 09 Jul, 2012 12:30 AM

   

   No

   • Edit

6. Support Staff 6 Posted by Brett on 09 Jul, 2012 12:36 AM

   

   If there's no external custom processor set up, then something may be wrong with the binary for Marked itself. I'm going to recommend deleting Marked using Launchpad (hold down Option and click the X). Go back to the App Store and go to Purchases and install again. Let me know if the problem persists.

   • Edit

7. 7 Posted by Cary Landholt on 09 Jul, 2012 12:45 AM

   

   I tried that before contacting you, but just in case I did it again, per your instructions. Still have the same results. I also verified the custom processor settings (see pic).

   • PastedGraphic-1.pdf 70.5 KB
   • Edit

8. Support Staff 8 Posted by Brett on 09 Jul, 2012 12:58 AM

   

   Ok, thanks for trying that. We'll need to try debug mode to see where it's crashing, then I'll have a better idea what might be going wrong;

   1. Open Terminal

   2. Type the following and hit enter (you can copy/paste):

         defaults write com.brettterpstra.marky debugMode 1
      

   3. Now tail your log file:

         tail -f /var/log/system.log | grep Marked
      

   4. Open a file in Marked
   5. Copy any output you get in Terminal and paste it here

   Thanks!

   • Edit

9. 9 Posted by Cary Landholt on 09 Jul, 2012 01:11 AM

   

   Jul 8 20:09:51 Cary-Landholts-Mac-Pro Marked[739]: Performance: Please update this scripting addition to supply a value for ThreadSafe for each event handler: "/Users/cary/Library/ScriptingAdditions/RFAgentExtension.osax"
   Jul 8 20:10:05 Cary-Landholts-Mac-Pro Marked[739]: Initial load from baseURL
   Jul 8 20:10:05 Cary-Landholts-Mac-Pro Marked[739]: Loading
   Jul 8 20:10:05 Cary-Landholts-Mac-Pro Marked[739]: README.md opened with encoding 4
   Jul 8 20:10:05 Cary-Landholts-Mac-Pro Marked[739]: An uncaught exception was raised
   Jul 8 20:10:05 Cary-Landholts-Mac-Pro Marked[739]: launch path not accessible
   Jul 8 20:10:05 Cary-Landholts-Mac-Pro Marked[739]: (
   5 Marked 0x000000010af23985 Marked + 55685
   6 Marked 0x000000010af24524 Marked + 58660
   7 Marked 0x000000010af1bb5b Marked + 23387
   10 Marked 0x000000010af18dcd Marked + 11725
   29 Marked 0x000000010af17dc4 Marked + 7620
   Jul 8 20:10:05 Cary-Landholts-Mac-Pro Marked[739]: *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'launch path not accessible'
   5 Marked 0x000000010af23985 Marked + 55685
   6 Marked 0x000000010af24524 Marked + 58660
   7 Marked 0x000000010af1bb5b Marked + 23387
   10 Marked 0x000000010af18dcd Marked + 11725
   29 Marked 0x000000010af17dc4 Marked + 7620
   Jul 8 20:10:06 Cary-Landholts-Mac-Pro ReportCrash[757]: Saved crash report for Marked[739] version 1.4 (221) to /Users/cary/Library/Logs/DiagnosticReports/Marked_2012-07-08-201006_Cary-Landholts-Mac-Pro.crash

   • Edit

10. Support Staff 10 Posted by Brett on 09 Jul, 2012 01:24 AM

    

    what do you get when you run this in Terminal?

     ls -l /usr/bin/ruby
    

    • Edit

11. 11 Posted by Cary Landholt on 09 Jul, 2012 01:39 AM

    

    lrwxr-xr-x 1 root wheel 76 Jul 21 2011 /usr/bin/ruby@ -> ../../System/Library/Frameworks/Ruby.framework/Versions/Current/usr/bin/ruby

    • Edit

12. Support Staff 12 Posted by Brett on 09 Jul, 2012 01:57 AM

    

    Unfortunately none of this has given me any clues so far. Has anything on your system changed recently? Upgrades, system utilities, etc.? I know you would have mentioned it already if there was anything major, but can you think of anything else that might have happened around the time Marked stopped working?

    Sorry for such an unscientific question, these crash reports and debugging measures just aren't making sense yet.

    • Edit

13. 13 Posted by Cary Landholt on 09 Jul, 2012 02:00 AM

    

    I appreciate your efforts, Brett. The only thing I can think of is that I upgraded Ruby and Rails semi-recently.
    I remembered this when you had me run the terminal command referencing Ruby.

    Other than that, I don't recall anything else.

    • Edit

14. Support Staff 14 Posted by Brett on 09 Jul, 2012 02:15 AM

    

    That could possibly be the issue. Around the point that it's crashing, Marked is calling out to Ruby to do some string handling. It looks for the default OS X ruby processor, and if that failed it would error out in a similar fashion (I need better error handling for that scenario, but I haven't run into it being an issue before). Did your upgrade modify the default Ruby, or are you using something like rvm or rbenv?

    It's odd that the symlink for Ruby appears to be correct and still have issues... what do you get if you run:

    /usr/bin/ruby -v

    and
    
    echo "Testing"|/usr/bin/ruby /Applications/Marked.app/Contents/Resources/removeMMDHeaders.rb

    Thanks for your patience in solving this.

    • Edit

15. 15 Posted by Cary Landholt on 09 Jul, 2012 02:18 AM

    

    It looks like you're on to something.
    After executing "/usr/bin/ruby -v" I receive the following:
    -bash: /usr/bin/ruby: No such file or directory

    There is not ruby directory in /usr/bin/

    • Edit

16. Support Staff 16 Posted by Brett on 09 Jul, 2012 02:30 AM

    

    Ok, run this:

    which ruby

    That will show you if there's a ruby processor in the path. If there is, run:

    ln -s [path to ruby from previous cmd] /usr/bin/ruby

    Let me know if the first command comes back with an error.

    -Brett

    • Edit

17. 17 Posted by Cary Landholt on 09 Jul, 2012 02:34 AM

    

    which ruby
    /Users/cary/.rvm/rubies/ruby-1.9.3-p194/bin/ruby

    ln -s "/Users/cary/.rvm/rubies/ruby-1.9.3-p194/bin/ruby" /usr/bin/ruby
    ln: /usr/bin/ruby: File exists

    • Edit

18. Support Staff 18 Posted by Brett on 09 Jul, 2012 02:45 AM

    

    Ok, so you have a broken symlink. That's the root of the problem. You're using rvm, so repairing that link shouldn't affect any of your other Ruby installs.

    Before I have you do anything, though, check and see if your system Ruby is still there:

     /System/Library/Frameworks/Ruby.framework/Versions/Current/usr/bin/ruby -v
    

    If it is there, remove the existing symlink:

     sudo rm /usr/bin/ruby
    

    You'll need to enter your default system password after running the command.

    Then link the system ruby back there:

     sudo ln -s /System/Library/Frameworks/Ruby.framework/Versions/Current/usr/bin/ruby /usr/bin/ruby
    

    If it's not there, then you have a larger problem. You should be able to solve it by linking your rvm 1.9.3 binary there, but you may run into other problems later. Given that the symlink is already broken, though, I don't think it can hurt to try this. Remove /usr/bin/ruby as above, then run:

     sudo ln -s  /Users/cary/.rvm/rubies/ruby-1.9.3-p194/bin/ruby /usr/bin/ruby
    

    If/when you upgrade your rvm install, it may break that link again. The only real fix for the problem is likely to reinstall OS X and restore the default frameworks.

    I'm not sure how you installed rvm, but it shouldn't have mangled the default Ruby like this (that's kind of the point of rvm). Not sure what else might have done it, though.

    • Edit

19. 19 Posted by Cary Landholt on 09 Jul, 2012 02:51 AM

    

    Brett - I will have to try that tomorrow.

    Thanks much!

    • Edit

20. 20 Posted by Cary Landholt on 10 Jul, 2012 03:42 AM

    

    Brett,

    Looks like /System/Library/Frameworks/Ruby.framework was missing. I restored from Time Machine. Along with your symlink fix, all is good, and Marked is back up.

    Thank you very much for spending your time on something unrelated to Marked. It is much appreciated.

    Thanks for Marked, by the way. I commit quite a bit to GitHub and love that you have the GitHub theme.

    Thanks again!

    Cary

    • Edit

21. Support Staff 21 Posted by Brett on 10 Jul, 2012 01:18 PM

    

    No problem, glad things worked out.

    • Edit