cmd/trace: split traces include all stack traces, which can consume all space #56444
Labels
compiler/runtime
Issues related to the Go compiler and/or runtime.
FrozenDueToAge
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
cmd/trace splits events into ~100MB chunks of JSON. When creating chunks, each chunk includes the full stackFrames map for the entire trace, rather than limiting to just the stack frames relevant to the events in the chunk.
In the most extreme case, the stackFrames map is >100MB of JSON, leaving no space for events. In this case, cmd/trace will include only 1 event in each split, resulting in thousands of ~useless splits.
It should be possible to mitigate this by including only relevant stack frames.
The text was updated successfully, but these errors were encountered: