Sublime Forum

Sublime Merge auto quitting

#1

Hello,

This issue has been bothering me for some time, now it’s time to raise an official report.

After some use, maybe days or weeks but sooner or later Sublime Merge will start auto quitting when executing basic command e.g. committing or staging files.

My feeling is that it starts after using it to handle more than one repo. Even though I always have just one repo/tab open.

Resetting the app by completely deleting the application support directory solves temporarily the issue.

When Sublime Merge quits, I have no error message or crash report. It just looks like it has received a quit command…

Changing git version does not have any effect.

Thank you,
Balint

Here’s my debug log:

=== App Version Information ===
Build: 2083

=== Git Version Information ===
Using Git: git (system)
git version 2.40.1
PATH: /opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/laps:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin (from shell)
environment variables loaded using: /bin/zsh -l

=== Browse Page Information ===
HEAD: 663c0a502150aec9152484ef32af75df730e6575
Is in merge: 0
Is in cherry_pick: 0
Is in rebase: 0
Is in revert: 0

=== Git Status Information ===

=== Our Status Information ===

=== Git Config Information ===
branch.feat/TI-1906/UI-setup.merge=refs/heads/feat/TI-1906/UI-setup
branch.feat/TI-1906/UI-setup.remote=origin
branch.feat/TI-1906/base-setup.merge=refs/heads/feat/TI-1906/base-setup
branch.feat/TI-1906/base-setup.remote=origin
branch.feat/TI-1922/code-improvements.merge=refs/heads/feat/TI-1922/code-improvements
branch.feat/TI-1922/code-improvements.remote=origin
branch.feat/TI-1922/color-code-avatars.merge=refs/heads/feat/TI-1922/color-code-avatars
branch.feat/TI-1922/color-code-avatars.remote=origin
branch.feat/TI-1922/group-notes-by-date.merge=refs/heads/feat/TI-1922/group-notes-by-date
branch.feat/TI-1922/group-notes-by-date.remote=origin
branch.feat/TI-1922/notes-list-header.merge=refs/heads/feat/TI-1922/notes-list-header
branch.feat/TI-1922/notes-list-header.remote=origin
branch.feat/TI-1975/base.merge=refs/heads/feat/TI-1975/base
branch.feat/TI-1975/base.remote=origin
branch.feat/TI-1975/custom-trackings-spreadsheet-title.merge=refs/heads/feat/TI-1975/custom-trackings-spreadsheet-title
branch.feat/TI-1975/custom-trackings-spreadsheet-title.remote=origin
branch.feat/TI-2077/goal-management.merge=refs/heads/feat/TI-2077/goal-management
branch.feat/TI-2077/goal-management.remote=origin
core.bare=false
core.excludesfile=/Users/./.gitignore
core.filemode=true
core.ignorecase=true
core.logallrefupdates=true
core.precomposeunicode=true
core.repositoryformatversion=0
credential.helper=osxkeychain
remote.origin.fetch=+refs/heads/
:refs/remotes/origin/*
remote.origin.url=git@.://***.git
user.email=******@***.***
user.name=****** *****

=== Our Config Information ===
Git Config Path Information
Using config path: /etc/gitconfig
Using config path: /Users/.****/.config/git/config
Using config path: /Users/
./.gitconfig
Using config path: /Users/*****.
/Work/pulsar/.git/config

Our config output is different to the Git config output
branch.feat/TI-1906/UI-setup.merge=refs/heads/feat/TI-1906/UI-setup
branch.feat/TI-1906/UI-setup.remote=origin
branch.feat/TI-1906/base-setup.merge=refs/heads/feat/TI-1906/base-setup
branch.feat/TI-1906/base-setup.remote=origin
branch.feat/TI-1922/code-improvements.merge=refs/heads/feat/TI-1922/code-improvements
branch.feat/TI-1922/code-improvements.remote=origin
branch.feat/TI-1922/color-code-avatars.merge=refs/heads/feat/TI-1922/color-code-avatars
branch.feat/TI-1922/color-code-avatars.remote=origin
branch.feat/TI-1922/group-notes-by-date.merge=refs/heads/feat/TI-1922/group-notes-by-date
branch.feat/TI-1922/group-notes-by-date.remote=origin
branch.feat/TI-1922/notes-list-header.merge=refs/heads/feat/TI-1922/notes-list-header
branch.feat/TI-1922/notes-list-header.remote=origin
branch.feat/TI-1975/base.merge=refs/heads/feat/TI-1975/base
branch.feat/TI-1975/base.remote=origin
branch.feat/TI-1975/custom-trackings-spreadsheet-title.merge=refs/heads/feat/TI-1975/custom-trackings-spreadsheet-title
branch.feat/TI-1975/custom-trackings-spreadsheet-title.remote=origin
branch.feat/TI-2077/goal-management.merge=refs/heads/feat/TI-2077/goal-management
branch.feat/TI-2077/goal-management.remote=origin
core.bare=false
core.excludesfile=/Users/./.gitignore
core.filemode=true
core.ignorecase=true
core.logallrefupdates=true
core.precomposeunicode=true
core.repositoryformatversion=0
remote.origin.fetch=+refs/heads/
:refs/remotes/origin/

remote.origin.url=
@
.com://.git
user.email=
**@***.***
user.name=****** *****

=== Git Attributes Information ===
git check_attr --all output

=== Our Modified Files Newline Normalisation and EOL Information ===

=== Our Modified Files Flag Information ===
Ignoring symlinks: 0

0 Likes

#2

The only workaround I’ve found is to

rm ~/Library/Application\ Support/Sublime\ Merge/Local/Auto\ Save\ Session.sublime_session ~/Library/Application\ Support/Sublime\ Merge/Local/Session.sublime_session

After that it seems to become more stable again.

0 Likes