You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Twice today I've seen a recently-compiled goimports spin off into using 1000+% CPU for minutes.
Specifically, I am using goimports from x/tools 4796d4b:
The first time I did kill -ABRT and found it was doing lots of file system scans,
which seemed not specific enough to file a report.
The second time I guessed it was the same and did lsof a few times.
It was scanning the standard library, repeatedly:
Twice today I've seen a recently-compiled goimports spin off into using 1000+% CPU for minutes.
Specifically, I am using goimports from x/tools 4796d4b:
The first time I did kill -ABRT and found it was doing lots of file system scans,
which seemed not specific enough to file a report.
The second time I guessed it was the same and did lsof a few times.
It was scanning the standard library, repeatedly:
You can see all the file descriptors ≥ 7 are getting recycled quickly.
Then I sent it an ABRT and got this dump:
I am not sure why it is scanning the standard library repeatedly in addExternalCandidates (as opposed to say addStdlibCandidates) but bugs are bugs.
/cc @ianthehat
The text was updated successfully, but these errors were encountered: