-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
runtime: "fatal error: runtime: pipe failed" on macOS Big Sur #44941
Comments
@VojtechVitek If you'd like to verify Go 1.16RC1, you can still install it via
|
Is this reproducible if you run natively on ARM64 (using a toolchain built with |
@cherrymui I can reproduce this on native arm64 build too (thanks for pointing this out!):
|
@toothrot I can reproduce this on Go 1.16rc1 too.
But I'm pretty sure I didn't run into this few weeks back.. Perhaps I might have updated Xcode Command Line Tools since then. |
I got different error on an Apple M1
|
I've tried with with 1.16.1 on M1 arm64 and could not repro within 60s for what it's worth:
|
@andig Thanks. Can you try again in a folder with many subdirectories and files? Perhaps this has something to do with the number of fsnotify (kqueue) files being watched. I was able to run @toothrot @cherrymui Is there anything else we can do or provide to help debug this issue? |
I've retried with 900k files (my home folder with lots of git repos inside). No crash. |
@VojtechVitek i'm seeing the same panic under some circumstances with Hugo (Intel, Mojave). Still trying to pin down why, exactly I did start trying prior Go versions and found that with Go 1.14 the panic (in the hugo case) was replaced with an error Using I haven't come up with a standalone test case as yet though. |
I had the same issue as @cuonglm and @VojtechVitek correctly pointed out the issue is due to watching big directories. I had a node_modules directory being watched by realize. Adding it into |
I can still reproduce this with Go 1.17.2.
|
Unresolved ! pls |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (
go env
)?Macbook Air M1 (Apple Silicon ARM64)
macOS Big Sur go1.16.1 darwin/amd64
go env
OutputWhat did you do?
What did you expect to see?
rerun -watch . -run echo "Rerunning command."
On any file-system change, the
echo
command would run. This works well on other architectures. And I'd swear this used to work on Go 1.16rc1. However I can't find it anymore in the Go Download page, so I can't re-test it.What did you see instead?
fatal error: runtime: pipe failed
I'm sorry if this is insufficient bug report, but I don't have a clue what else to include. I'm not sure how to help debug this any further. Any help/guidance would be greatly appreciated.
During the crash, the program does this in the high-level:
os/exec
command in the backgroundsignal.Notify
)time.NewTimer()
)https://github.com/VojtechVitek/rerun
The text was updated successfully, but these errors were encountered: