jesseduffield / jesseduffield/lazygit

Memory climbed to 9.6GB while laptop closed

Open
#2,460 26 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Go
Stars
82.4k
Forks
3k
Avg merge
2d 18h
Merged PRs (30d)
19

Description

**Describe the bug**
My memory usage climbed to 9GB while my laptop was closed. See screenshot.
This issue has never occurred before, but I am not a user very often.

**To Reproduce**
Precise steps unknown.

1. I started lazygit as normal and performed some amend & reword message commands.
2. I closed my laptop's lid and left the range of WiFi. The battery was high enough such that the OS maintained state.
3. I reopened my laptop with lazygit at 9.6GB, slowing my entire system down.

**Expected behavior**
lazygit usually operates at around 20MB idle, around 500X less memory than what was being used just now.

**Screenshots**
![](https://i.xevion.dev/2023/02/ProcessHacker_v2rNSbP6qD.png)

I do not know the difference between the two chosen processes, but the 9.6GB process closed and went away as soon as I pressed q in the terminal. The application was still responsive, it seems.

**Version info:**
`commit=d1a8b05401ccda1e52215203139a252eb3be3b79, build date=2022-11-14T09:22:31Z, build source=binaryRelease, version=0.36.0, os=windows, arch=amd64, git version=2.35.1.windows.2`
`git version 2.35.1.windows.2`

**Additional context**
- I was using lazygit in combination with Webstorm, working on [this](https://github.com/Xevion/rdap/tree/hook-rewrite) repository.
- I was running lazygit inside Windows Terminal on Windows 11, launched from Powershell 7.2.9.
- I work on a Lenovo X1 Carbon Gen 6, with 16GB of RAM.

The only idea I have is that lazygit was somehow making network requests (git fetch) in the background, and they were failing continuously or not being made properly. I left the area I was in, thus disconnecting from WiFi. My laptop should not reconnect to WiFi until it is opened, I would believe.

I know this isn't a great bug report, no logs afaik to go off, but I'm curious if you've had any similar reports.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.