There seems to be a step missing between 5 and 6 as it is unclear (at least to me) how IIS is involved when executing the sample go program shown on Windows. Does just executing the hello.exe from command line on Windows result in 100% CPU?

If there are more steps involved please provide a complete reproduction. Note that the problem might not fall in the realm of the Go programming language.

No more steps involved, in fact there is no any relations between hello.exe and IIS. But when I run hello.exe in command line, the cpu of IIS must reach to 100%, and when hello.exe exited, the cpu also restored to normalize.

So you are essentially saying running process X makes process Y consume 100% CPU. I don't see any Go specific issue here as you have clearly mentioned there is no relation between hello.exe and IIS.

This may be an environment issue, or something else. I would suggest you to take a look at the Questions wiki page; it has a list of good places for asking questions such as these.

Note that the issue tracker is only used to track bugs/proposal in Go.

Note that the example program doesn't even build: https://play.golang.org/p/B1ytJHfLAxs

If you believe that this is a bug in the Go runtime, then we need explicit steps that we can follow exactly to reproduce the problem. Given the lack of relationship between the two programs, I'm inclined to suspect that the bug lies elsewhere: for example, do you have an antivirus program running that may be consulting the IIS process to check for signatures matching hello.exe?

Maybe it's due to Go changing Windows' global timer resolution. (#28255)

Maybe it's due to Go changing Windows' global timer resolution.

If it's true, how to fix it?

@hcj116, I suppose you could try doing something like this comment: #28255 (comment) and resetting it back to the system default.

Yes, you're right. I encountered the same issue.

When I unset the automatically synchronization with Internet time server, the system clock runs faster than usual.

I would advise you to add your observations to that thread.

Duplicate of #28255