Sublime Forum

**wbond** · July 26, 2016, 10:27am

Thanks for this bit. I’ll see if I can reproduce using that on my end.

What version of OS X are you using?

**teoric** · July 26, 2016, 12:08pm

What version of OS X are you using?

Sorry, 10.10.5 (14F1808). And thanks for looking into this!

**kapooostin** · July 26, 2016, 12:38pm

Deletion of a session file has helped to start Sublime. Changelog crashes my OS X 10.10.5.

**kaosmos** · July 26, 2016, 12:48pm

Looks like it is definitely the changelog window that crashes Sublime in OS X 10.10.5

I edited the Session.sublime_session (in ~/Library/Application Support/Sublime Text 3/Local/ as suggested by @wbond) by hand and modified the value of last_version to 3119, so the editor doesn’t show the changelog window anymore and it starts flawlessly.
But as soon as you try to open the changelog, Sublime closes itself immediately.

**louim** · July 26, 2016, 7:04pm

I can confirm the same thing worked for me. I’m also running 10.10.5 (14F1808)

**wbond** · July 26, 2016, 10:08pm

I just set up a 10.10.5 VM, however I can’t reproduce the crash with 3119. I’ll be digging some more on this.

**jps** · July 27, 2016, 4:34am

OS X will generally save a crash report that you can access via the ‘Console’ application, if there’s a crash report there for Sublime Text that would be very helpful

**mrmachine** · July 27, 2016, 4:50am

This worked for me too. Thanks. Running 10.10.5 (14F1909)

**teoric** · July 27, 2016, 6:11am

Unfortunately, this seems to be a special case, not a general one: I have no reports in Console, ~/Library/Logs/ or /Library/Logs/.

**jps** · July 27, 2016, 7:33am

@teoric thanks for looking into it. Can you let me know if entering any of these lines in Sublime Text’s console causes a crash?

view.show_popup('<div style="font-family: monospace">hello</div>')
view.show_popup('<style>div { font-family: "Open Sans", "Helvetica Neue", Helvetica, Arial, sans-serif }</style><div>hello</div>')```

**kaosmos** · July 27, 2016, 7:45am

I edited the session file to recreate the error condition but Sublime doesn’t generate a crash report, as stated by @teoric.

**kaosmos** · July 27, 2016, 7:48am

@jsp I tried all the strings and no one causes the crash

**kaosmos** · July 27, 2016, 7:50am

Maybe this can add some bits: when Sublime crashes it shows the changelog windows, so it seems to be able to render it.

**teoric** · July 27, 2016, 8:15am

None of them causes a crash, but there is also no popup. And @kaosmos is right: The Changelog is displayed briefly for a moment before the crash.

**kaosmos** · July 27, 2016, 8:22am

I see a popup when I input the strings, it is just a little “hello” in the middle of the editor, maybe if you have a light theme it is not so easy to spot.

**nkrim** · July 27, 2016, 5:59pm

I had the same issue, which was fixed w/ the solution of changing the latest_version, but sublime still crashes randomly during use, usually while switching tabs. I can never catch what the error is in the console (if there is any), so I’m not sure what the cause could be, though it could potentially be a plugin, so I’m wondering if anyone else is experiencin the same thing. I’m on OSX 10.10.5 as well.

**nkrim** · July 28, 2016, 12:05am

I installed a logger plugin and even that can’t capture the error that causes the crash, so I’m at a loss right now. I think I’ll try and do a full restart as mentioned originally.

Edit 1: I did a full restart of sublime and it still crashes randomly, I’m going to remove all the plugins now and see if that persists.

Edit 2: Everything works well without the plugins/packages so I suppose this is out of the scope of sublime itself, and rather involves whichever plugin is causing this, so cya

**wbond** · July 28, 2016, 7:30pm

This issue should be resolved by build 3120. If you are still having trouble, please let me know.

**teoric** · July 28, 2016, 8:49pm

Fixed for me – thank you very much!

**kaosmos** · August 2, 2016, 9:54am

Fixed for me too, thank you

Build 3119 crash or freeze on OS X 10.10