search

sublimehq / sublime_merge

Issue tracker for Sublime Merge
https://www.sublimemerge.com
273 stars 14 forks source link

Sublime Merge drives system OOM #1718

Open stdedos opened 1 year ago

stdedos commented 1 year ago

Hi @stdedos,

Thank you for providing this information - this will help us narrow down the cause of the issue and investigate a fix as soon as possible.

When you have a spare moment, could you provide the following information:

  • Did you notice this issue happening after an upgrade to a specific version? If so, which version?

2068 -> 2071, but downgrading doesn't help

  • Could you run git count-objects -vH on the largest of the repositories, and share the output
$ git count-objects -vH
count: 1476
size: 60.08 MiB
in-pack: 68748
packs: 10
size-pack: 503.07 MiB
prune-packable: 86
garbage: 0
size-garbage: 0 bytes
  • You mention some large files that are not being tracked under Git LFS. Could you give a rough indication of how large these files are (1MB, 100MB, 1GB etc).

image

But never have I ever mentioned LFS.

  • Could you share your Sublime Merge debug information, while the repository (that triggered the OOM error) is open and in focus.

I don't know which one it is. I don't keep track of how I use the program while using it. Here's an approximation:

=== App Version Information ===
Build: 2071

=== Git Version Information ===
Using Git: git (system)
git version 2.25.1
PATH: /home/stdedos/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin

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

=== Git Status Information ===
?? 1
?? 2
?? 3
?? 4
?? 5
?? 6

=== Our Status Information ===
?? 1
?? 2
?? 3
?? 4
?? 5
?? 6

=== Git Config Information ===
...

=== Our Config Information ===
Git Config Path Information
Using config path: /etc/gitconfig
Using config path: /home/stdedos/.config/git/config
Using config path: /home/stdedos/.gitconfig
Using config path: /home/stdedos/..../.git/config

Our config output is identical to the Git config output

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

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

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

However, if you have actually OOMed your system (or successfully e.g. fork-bombed it), you'd now that collecting information during oom-killer trying to salvage your system is simply. not. possible.

This can be accessed via Help > Debug Information. Before sharing this information, please redact anything you consider confidential (file paths, remote names, Git user information etc).