Chris McDonnell

Could be related to https://github.com/jesseduffield/lazygit/issues/2460, where the root cause has not been found. Can you check in on your memory usage prior to the crash? Additionally is the issue also...

/close Closing as part of an issue backlog cleanup, and it seems this issue was fixed shortly after it came out. Feel free to re-open if I'm wrong

I just ran the master branch of lazygit with go `1.23.6` with `go run main.go -debug`: ``` godebug ( default=go1.22 asynctimerchan=1 ) ``` inside of `go.mod`, and still received `POTENTIAL...

My apologies, our problem was because we were on version `v0.3.1` of this library, which included a version of `goid` prior to their support for go 1.23. This manifested itself...

@jesseduffield Ran the code locally, and it's certainly better! Although it moves me from a file named error  to  The latter could 100% be user-error on my part....

Can you clarify what terminal you use? A lot of emoji problems can be related to that. And what does the diff look like in your terminal when you just...

I cloned your repo, and when I run it inside of WSL2 in Wezterm, it looks totally fine. When I launch tmux, that's when the issue comes in. Inside TMUX:...

@mrmerc Hey, thanks for the report! Easy to reproduce. I'm curious, is this an actual standard part of your flow, or did you just discover it while messing around? I'm...

Okay, interesting! Well, the fix ended up being pretty easy in this case https://github.com/jesseduffield/lazygit/pull/4583 I also added a 2nd commit just now (while typing this) to that PR that also...

/close I believe this has now been implemented, see https://github.com/jesseduffield/lazygit/pull/4501