Unfortunately I don’t have any debug logs, but in the space of say, half an hour, I’ve had three lockups - two within 2 minutes of each other.
I don’t like reports like these - how do I turn on debugging?
Unfortunately I don’t have any debug logs, but in the space of say, half an hour, I’ve had three lockups - two within 2 minutes of each other.
I don’t like reports like these - how do I turn on debugging?
Same problem here (OSX). A simple copy paste between two C++ files cause a 100% CPU usage.
Downgraded to #3194
Same thing here. Both happened when I had the find menu open.
I have saved a log from when I force quitted sublime but I’m not sure if it contains any sensitive info. If anyone could use this log to fix the issue let me know.
I also got serveral freezes today, when switching between windows, use the ctrl+p dropdown etc.
Xubuntu 18.04.2 LTS
Me too! Running Xubuntu 18.04, have to force quit and restart to make it usable again.
Same issue (Win 10): first time while searching with F3, second time I just hit enter in the autocompletion window (no find menu open at this moment)
Happens for me as well, macOS 10.13.6.
Repro that works for me every time, open a file from disk/project, scroll to the bottom by navigating via the minimap. -> instant 100% lockup.
Same here. It freezes reliably as soon as I search for a specific file with CTRL+P after start-up, but also under other random circumstances. (Win 10)
We get so used to Sublime’s dev builds being solid that when something bad like this gets through it’s a shock!
Just had my first of these as well. This update may be worth rolling back!
My sublime keeps hanging here on linux too with latest dev build. Had to kill 3 times in last 30 mins. (build 3195)
I had the same issue with 3195 on macOS 10.14.3. I rolled back to 3194 what is working perfectly.
Yeah, me too. It seemed to be working for me last night for a while, but couldn’t even get it launched this morning. Crashed on launch 4 times in a row. Reverted to 3194 and is working fine. macOS 10.14.3
Same here, on build 3195, both Linux x64 (Ubuntu 19.04) and Windows 10. At first I blamed myself as I was trying out switch expressions on java 12, which might be expected to break syntax colouring a bit (it does, a bit), but the crashing occuring on other more innocent pursuits, and the other posts on this forum, suggest otherwise.
Just wanted to let you all know we are working on getting this sorted and making a new release.
Wow, liked everyone else super shocked it was broken. i don’t ever think this happened to me before. Keep up the good work, best fucking editor ever. I really don’t mind. Just sending some love and all that before rolling back!