Is there code internal to the runtime that shuts down all of its threads at the end of the process, or does it just rely upon the OS to do the cleanup?
I'm asking for a Windows DLL unload situation, hoping to be able to unmap the runtimes memory without having it crash the main program on DLL unload. As a workaround last year I pinned the DLL permanently into Windows memory, but that hack is starting to crack around the edges. If not, I suppose I can just try to manually kill them with the windows API, TerminateThread(); if I can find their handles. Which begs the question... is there a way to locate the Go runtime/all user goroutine threads (in Windows)? Thanks! -- 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/4bc81e9a-c08a-495a-ad7b-1c1a5fe89cbe%40googlegroups.com.
