Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
runtime: threadcreate profile is broken #6104
What is a "useful stack"? I've attached threadcreate profile from HTTP server FTR. Lots of threads are created by sysmon (not useful). Timerproc created 3 threads (not useful). Creation of random goroutines caused thread creation up to GOMAXPROCS (not useful). I can imagine an end user trying to figure out what threadcreate profile is trying to say... It must be centered around blocking syscalls and locked threads. But which exactly? Probably all, because they all can trigger thread creation. It all needs to be rethought and probably even renamed. Probably now it's better to just remove it.
Im currently debugging kubelet binary (too many threads) and need to get stack dump for the cause. Is threadcreate profile known to dump correct stack with golang 1.8 (go version go1.8.1.typealias linux/amd64) ? I tested out with simple cgo wrapper (C.sleep(100)) and currently threadcreate profile shows number of threads create but no stack dump.