-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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/cgo: pthread_create failed: Resource temporarily unavailable on freebsd/386, netbsd/arm #5233
Labels
Comments
Seems like it depends on the number of goroutines, funny. If we change L61 of crash_cgo_test.go, https://code.google.com/p/go/source/browse/src/pkg/runtime/crash_cgo_test.go for example s/64/32/, then test passes. |
Never mind, or must be worried more, not sure. Just tried the build w/ source but failed to repro. (and C/C++ w/ or w/o boost but includes pthread works fine; it runs up to 100+ threads, I mean, num of filedescs and stacksize per process configuration are enough to run pthread stuff.) What? The only difference btw last night and now would be... VM slept and resumed. Hm... WDYT? Can you want to hold this issue or to mark as retracted? |
the runtime test still fails for netbsd/arm. http://build.golang.org/log/b2a854589f11337dee2617e71f3c3e5ed66537d1 what information do you want? |
> Ans. 1 - yes, as mentioned at #5 #5 says that it's possible to create threads with C/pthread, but at the same time [Go] build from source works as well. So it says nothing. What I want is: Go create 1000 threads -> fail C/pthread create 1000 threads -> OK Go create 1000 threads -> fail C/pthread create 1000 threads -> OK Go create 1000 threads -> fail C/pthread create 1000 threads -> OK Go create 1000 threads -> fail C/pthread create 1000 threads -> OK What we have is: Go create 1000 threads -> fail day later: C/pthread create 1000 threads -> OK Go create 1000 threads -> OK |
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The text was updated successfully, but these errors were encountered: