forked from bazelbuild/bazel
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
When outputting a thread dump for a slow interruption, group threads …
…with the same stack trace together, sort the dump by stack length (longer stacks are more likely to be interesting), and insert the longest stack in the remote bug report, for easier triage. Also log stack traces and thread names in one single logline: makes it much easier to read these lines and to search over them. The length should still be manageable, and if there are thousands of threads for a single stack trace, it's unlikely they're doing anything very interesting. I didn't try too hard to minimize CPU/garbage, but if some of the slow interrupts are due to an overloaded server, it's possible this will have some negative effects and need to be optimized. PiperOrigin-RevId: 388311331
- Loading branch information
1 parent
262cd8a
commit 8eba488
Showing
1 changed file
with
109 additions
and
13 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters