Haven't found any information about what the goroutine "numbers" in a stack trace mean exactly. A Google search brings up some references about interpreting stack traces and posts that seem to indicate that numbers are resused, but no definitive question and answer asked that I can find.
Are the numbers shown in a Go stack trace reused or are they incremented? If I see a large number does that mean there are at least that many goroutines currently alive?
For example, consider the following stack trace:
goroutine 127590 [running]:
crypto/sha256.(*digest).checkSum(0xc042bb57d8, 0x0, 0x0, 0x0, 0x0)
/usr/local/go/src/crypto/sha256/sha256.go:247 +0x26d
Does this mean there are 127590 goroutines currently running?
If the king is named Henry VIII, does this mean that Henrys I to VII are still alive? These are just numbers to distinguish one from another.
It is an id of goroutine. You cannot conclude that it is a number of alive goroutines. It is similar to the process id in the operating system. The ids are cached and some may not be used.
To see how id of goroutine is generated search for goidgen in Go source code.
In Linux only process 0 is special in Go only goroutine 1 (main) is special.
See Why is there no goroutine ID?
Goroutines do not have names; they are just anonymous workers. They expose no unique identifier, name, or data structure to the programmer. Some people are surprised by this, expecting the go statement to return some item that can be used to access and control the goroutine later.