Il 05/04/22 19:09, Ian Lance Taylor ha scritto:
> It works fine for me either way, on Linux kernel 5.15.15.  What system
> are you running on?  What version of Go?  What version of
> golang.org/x/sys/unix?

Well, I tried it only on the playgound because it seems to reproduce the 
bug there, so I didn't bother to try on my machine.
Now I tried and indeed it runs fine for me too (linux 4.15.0 - go 1.18).

BTW even if the trimmed-down example seems to work fine (at least 
outside of the playground) I still see the bug in my full project, it is 
composed of many pieces that needs to run together to actually reproduce 
it, it's a bit hard to post here. :-(

I tried to pprof the application, and this is the state when it locks 
https://pastebin.com/raw/L1wa5hz6 basically everything is waiting on 
mutex, except the last goroutine that is trying to do a unix.Close(..) 
(and it is supposed to unlock everything else when done, but it's 
blocked for some reason an it never returns).

syscall.Syscall+0x4    go1.18/src/syscall/asm_linux_amd64.s:20
/sys/unix.Close+0x2f 
go/pkg/mod/golang.org/x/sys@v0.0.0-20220405052023-b1e9470b6e64/unix/zsyscall_linux.go:571

this is the version of x/sys:

        golang.org/x/sys v0.0.0-20220405052023-b1e9470b6e64 // indirect

C

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/0102017ffb2c9dc1-f0e9c7a6-9da4-46c0-8876-f229cbbb20fe-000000%40eu-west-1.amazonses.com.

Reply via email to