Sublime Forum

Version 4158 segfault but not in safemode - how to investigate?

#1

Installed version 4158 this morning and it segfaulted almost straight away after opening a file. subl --multiinstance --debug confirms it’s a segfault but the logs before hand do not offer anything revealing. I tried adding --safe-mode and could not make it crash after so I assume it’s something to do with plugins.

this is ubuntu 20 in via wsl 2

Any idea what to look at next?

these were the lines it consistently ended with upon repeat attempts

[30967:30967:20231019,195956.385634:ERROR file_io_posix.cc:144] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2)
[30967:30967:20231019,195956.385694:ERROR file_io_posix.cc:144] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2)
[30967:30968:20231019,195956.386814:ERROR directory_reader_posix.cc:42] opendir /home/david/.cache/sublime-text/Crash Reports/attachments/f99fb724-4b9d-4027-b612-e7161a5a5e95: No such file or directory (2)
Segmentation fault

edit: one time it said this too
libc++abi: terminating due to uncaught exception of type std::bad_alloc: std::bad_alloc

0 Likes

#2

Fixed in 4159 :man_shrugging: that’ll do

1 Like