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
net/http: send on closed channel #3793
Labels
Comments
Owner changed to @bradfitz. |
Fix at http://golang.org/cl/6347061 Labels changed: removed priority-triage. Status changed to Started. |
This issue was closed by revision 8a2a501. Status changed to Fixed. |
I'm back with a 32 core SB machine. This doesn't seem fixed at tip... go version weekly.2012-03-27 +6eb7e61b5286 GOMAXPROCS=20 Attachments:
|
Sigh. I can reproduce. Note to self: maybe fixed by http://golang.org/cl/6430056/ (currently unreviewed) Status changed to Accepted. |
I can trigger this bug within a few iterations with the following procedure, on a core i5 cd $GOROOT/src/net/http export GOMAXPROCS=81 go test -c while ./http.test ; do true; done Albert, can you please try http://golang.org/cl/6445069 ? |
Ran into fun with this test running in a loop: === RUN TestStressSurpriseServerCloses-81 --- FAIL: TestStressSurpriseServerCloses-81 (40.28 seconds) transport_test.go:440: presumed deadlock; no HTTP client activity seen in awhile lots of this in dmesg: [597413.388285] net_ratelimit: 16 callbacks suppressed [597413.388359] nf_conntrack: table full, dropping packet. [597413.661436] nf_conntrack: table full, dropping packet. [597414.161433] nf_conntrack: table full, dropping packet. This is on a relatively standard Fedora 16 machine with basic iptables rules. No sends on closed channels though. It seems that maybe the conntrack stuff should be disabled on busy systems. http://blog.sam-pointer.com/tag/nf_conntrack:tablefull,droppingpacket |
I'm assigning this bug to myself. http://golang.org/cl/6445069 fixes the issue but may require an additional test before submitting. Owner changed to @davecheney. |
This issue was closed by revision 2bdc60f. Status changed to Fixed. |
Issue #3861 has been merged into this issue. |
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
by dvyukov@chromium.org:
The text was updated successfully, but these errors were encountered: