Thanks, I just had a look and it is very similar to the output of http://127.0.0.1/debug/pprof/goroutine?debug=2 which I can already get to and I can’t see where the lock is left open!
On Wed, Jan 25, 2017 at 9:17 PM Tamás Gulácsi <tgulacs...@gmail.com> wrote: > 2017. január 25., szerda 19:09:36 UTC+1 időpontban l...@pinkfroot.com a > következőt írta: > > I seem to have an issue with logic in my code as from time to time it will > totally lock up the application and doing a dump of the goroutines shows > that they are all in the semacquire state. > > Is there any way without littering the console with logs to determine what > had left the lock open at all? > > The go race detector comes up with nothing at all when this occurs. > > > Send HUP (kill -HUP pid or pressing Ctrl+\ on the terminal), when the > program is locked up, save the resulting stack trace, and inspect. > It'll list all running/blocked goroutines, and the point of the wait, too. > -- 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. For more options, visit https://groups.google.com/d/optout.
