-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fatal error: all goroutines are asleep - deadlock! #3880
Comments
Your reproduction recipe shows pretty much basic, normal lazygit usage as far as I can tell. There must be something more that is specific to your setup, otherwise lazygit would be unusable for everybody. Are you starting lazygit from within a git repo? Does the problem happen for all your repos, or only certain ones? Have you checked if an official build (e.g. the homebrew version) has the same problem? |
Yes, a good example is the mantinedev/mantine repo I've cloned. It also happens to one of my own repos.
Yes, have tried using the Homebrew version and I still get the same error. On a tangent, with the steps above, I don't get this error on an Apple Silicon. Though when running |
I was looking into #3903 and ran into this issue with a binary compiled from a local checkout. Here's the trace from two different attempts: Attempt 1
Attempt 2
For what it's worth, this was only when running a locally compiled version: The downloaded version runs fine: |
I've just seen this after a clean clone of the lazygit repo, setting up the devcontainer, then running However, it doesn't happen without I also can't run any of the integration tests, which is making contributing something somewhat challenging... |
FWIW, |
Potentially connected to sasha-s/go-deadlock#38 |
- **PR Description** This PR solves #4002, and perhaps #3880 (if they are indeed duplicates), and the error message preventing debugging in #3973. The problem is that our version of `go-deadlock` transitively depends on a version of `goid` that predates their changes to support go `1.23`, which results in every goid being the number `2` for some reason. Bumping the version of `go-deadlock` to include the updated transitive dependency means that the goids are now correct, and `go-deadlock` does not confused why goroutine 2 is trying to lock so many things. I know very little about go vendored dependencies, so all I have done is edit the `go.mod` entry for `go-deadlock` to be v0.3.5, and then run a `go mod tidy` and `go mod vendor`. If there is a more correct way to bump a vendored dependency, feel free to close this PR and just do that!
Describe the bug
fatal error: all goroutines are asleep - deadlock!
To Reproduce
Steps to reproduce the behavior (macOS Sonoma latest version, latest go installation from its website):
go install github.com/jesseduffield/lazygit@latest
Expected behavior
Open LazyGit interface
Version info:
lazygit version
commit=, build date=, build source=unknown, version=unversioned, os=darwin, arch=amd64, git version=2.46.0
git version
git version 2.46.0
Additional context
Running on macOS Sonoma 14.6
Have added ~/go/bin to $PATH as instructed.
POTENTIAL DEADLOCK: Recursive locking:
when runninglazygit --debug
The text was updated successfully, but these errors were encountered: