Sublime Forum

Sublime and Smerge crash

#1

I’m running a licensed (expired) version of Sublime Text (build 4192).
Recently, my Subl crashed very frequently. I noticed that it crashed when I was running an other program. It didn’t crash on its own.
This program is called Vivado which compiles code for hardware. This runs very intensively on multiple CPUs.
I don’t know whose fault that is: Fedora (6.2.15-100.fc36.x86_64), Sublime Text (4192) or the Vivado program.
Where can I find more information about the crash or upload the crash data to you for support?
I notice that Sublime Text and Smerge (Build 2102) always crash at the same time.
Thank you!

0 Likes

#2

Crash reports are located in .cache/sublime-text/Crash Reports/. Inside the completed folder you should find the crash reports that have been uploaded. If you share the name of those crashes I can look them up.

0 Likes

#3

Thanks. All of them are empty
copmleted, attachements, new, pending :expressionless:

0 Likes

#4

Strange, that would indicate that they’re not crashing. Are you perhaps running out of memory? You could try running ST in a terminal using subl --multiinstance --debug to see what gets logged when it crashes.

0 Likes

#5

Thanks. Let me monitor the debug. There are awful lot of python error in the logs. It hasn’t crashed so far.

0 Likes

#6

It seems like the whole terminal where i launched the subl just disappear.
When I “tee” the output to a log these are the last errors:

Flake8Lint ERROR: /home/jeffl/.config/sublime-text/Packages/Python Flake8 Lint/contrib/pep8.py:109: FutureWarning: Possible nested set at position 1
Flake8Lint ERROR: EXTRANEOUS_WHITESPACE_REGEX = re.compile(r'[[({] | []}),;:]')
Flake8Lint ERROR: Traceback (most recent call last):
Flake8Lint ERROR: File "/home/jeffl/.config/sublime-text/Packages/Python Flake8 Lint/lint.py", line 35, in <module>
Flake8Lint ERROR: from pydocstyle import (
Flake8Lint ERROR: File "/home/jeffl/.config/sublime-text/Packages/Python Flake8 Lint/contrib/pydocstyle.py", line 20, in <module>
Flake8Lint ERROR: from collections import defaultdict, namedtuple, Set
Flake8Lint ERROR: ImportError: cannot import name 'Set' from 'collections' (/usr/lib64/python3.10/collections/__init__.py)
SublimeLinter: sublime_linter.py:334  Delay linting 'AxiInterface.py' for 0.3s
SublimeLinter: sublime_linter.py:334  Delay linting 'AxiInterface.py' for 0.0s
SublimeLinter: sublime_linter.py:352  No installed linter matches the view.
Flake8Lint ERROR: /home/jeffl/.config/sublime-text/Packages/Python Flake8 Lint/contrib/pep8.py:109: FutureWarning: Possible nested set at position 1
Flake8Lint ERROR: EXTRANEOUS_WHITESPACE_REGEX = re.compile(r'[[({] | []}),;:]')
Flake8Lint ERROR: Traceback (most recent call last):
Flake8Lint ERROR: File "/home/jeffl/.config/sublime-text/Packages/Python Flake8 Lint/lint.py", line 35, in <module>
Flake8Lint ERROR: from pydocstyle import (
Flake8Lint ERROR: File "/home/jeffl/.config/sublime-text/Packages/Python Flake8 Lint/contrib/pydocstyle.py", line 20, in <module>
Flake8Lint ERROR: from collections import defaultdict, namedtuple, Set
Flake8Lint ERROR: ImportError: cannot import name 'Set' from 'collections' (/usr/lib64/python3.10/collections/__init__.py)
SublimeLinter: sublime_linter.py:334  Delay linting 'AxiInterface.py' for 0.3s
SublimeLinter: sublime_linter.py:334  Delay linting 'AxiInterface.py' for 0.3s
SublimeLinter: sublime_linter.py:352  No installed linter matches the view.
SublimeLinter: sublime_linter.py:334  Delay linting 'AxiInterface.py' for 0.3s
SublimeLinter: sublime_linter.py:334  Delay linting 'AxiInterface.py' for 0.3s
SublimeLinter: sublime_linter.py:352  No installed linter matches the view.
SublimeLinter: sublime_linter.py:334  Delay linting 'AxiInterface.py' for 0.3s
0 Likes

#7

If the whole terminal gets killed then my suspicion is you’re running out of memory and Linux’s OOM killer is picking Sublime Text to free up memory.

0 Likes

#8

Yeah, very likely, as the program I run suck up quite a lot of memory.
Is there anyway to confirm?

0 Likes

#9

It should be getting logged, check sudo dmesg | egrep -i 'killed process'

1 Like

#10

There’s nothing in the log :expressionless:

0 Likes