cmd/trace - Go Issues

Go Issues Packages

cmd/trace

support splitting in goroutine viewFeatureRequestNeedsInvestigation

#51349 opened 2 months ago by prattmic

0

add a name/desc to goroutines which are inactive when get a pprof traceNeedsFix

#49994 opened 5 months ago by yifhao

4

provide a per-M viewDebuggingFeatureRequestNeedsInvestigation

#44074 opened 1 year ago by prattmic

5

grey colour is undocumented in goroutine analysisDocumentationNeedsDecision

#36232 opened 2 years ago by RealBar

2

Mininum mutator utilization plot window durations range is not consistent across Include optionsNeedsInvestigation

#35330 opened 2 years ago by egorbunov

1

problems and proposed improvementsNeedsInvestigation

#33322 opened 2 years ago by jcorbin

1

generate trace graph for custom region selectionFeatureRequestProposalProposal-Accepted

#30895 opened 3 years ago by AlexRouSg

17

"failed to parse trace: no consistent ordering of events possible"NeedsInvestigation

#29707 opened 3 years ago by 256dpi

23

provide aggregate 'go tool trace' goroutine analysis viewNeedsInvestigation

#29103 opened 3 years ago by robaho

19

does not track or report in-syscall properly NeedsInvestigation

#28996 opened 3 years ago by robaho

8

go tool trace mishandles goroutine that extends beyond the current span.NeedsFixhelp wanted

#21911 opened 4 years ago by davecheney

3

add 'greedy goroutine diagnosis' optionProposalProposal-Hold

#20792 opened 4 years ago by hnes

35

include CPU profile samplesFeatureRequestNeedsFix

#16895 opened 5 years ago by rhysh

2

execution tracer is essentially not documentedDocumentation

#16526 opened 5 years ago by AlekSi

6

the trace command should not contain hardcoded javascriptNeedsFix

#16377 opened 5 years ago by jcorbin

7

view large trace all at onceFeatureRequest

#11520 opened 6 years ago by josharian

16