My guess is your program is hanging because the garbage collector cannot run, and the garbage collector cannot run because all goroutines have not stopped.

Dup of #10958

@randall77 Is this issue really duplicated with #10958? Here I'm wondering why it hangs, while in #10958, I doubt the precise preempt happens at the newstack() but not every function call.

Yes. As Dave said, GC eventually tries to run, successfully stops the goroutine running test2, and then hangs forever trying to stop the goroutine that is doing for { test() }.

Why removing time.Now() from test2() works? Because then the whole program running would not trigger GC?
In other words, if the program has such infinite blocking loop, and if GC runs, then it would result in hanging?

Removing time.Now() from test2 doesn't work for me. The program still hangs after a while (~250K iterations).

Bottom line, don't write loops like this. Add runtime.Gosched() if you don't have anything else significant in the loop.

If performance is a concern unroll the loop or add an inner loop. Until we
teach our compilers how to do this automatically this work around is the
best advice we can give.

On Wed, Sep 9, 2015 at 11:38 AM, Keith Randall notifications@github.com
wrote:

Removing time.Now() from test2 doesn't work for me. The program still
hangs after a while (~250K iterations).

Bottom line, don't write loops like this. Add runtime.Gosched() if you
don't have anything else significant in the loop.

—
Reply to this email directly or view it on GitHub
#12553 (comment).

Yes, removing the time.Now() doesn't work.
The go 1.5.1 would hangs the program at ~250K iteration, and the go 1.3.3 would hangs at ~12million.

Then the backtrace would be:

goroutine 1 [running]:
main.main()
    /tmp/tmp.go:29 +0xb1

goroutine 5 [runnable]:
fmt.Println(0xc82003af80, 0x1, 0x1, 0x4c0c00, 0xc820487020, 0x0)
    /usr/local/go/src/fmt/print.go:263
main.test2()
    /tmp/tmp.go:12 +0xc8
created by main.main
    /tmp/tmp.go:26 +0x3c

Thanks for your advises.

I'm still wondering, the preemption check only happens at newstack(), right?

@kingluo this issue is closed. If you want to discuss it further, please open a thread on the golang-nuts mailing list.

Preemption checks happen at every function entry point, except those functions which don't have a preemption check (those with small stack frames, not recursive, ...).

The preemption check causes the function entry to call into morestack and then newstack where the preemption is processed.