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
Use go tool trace on the trace from #19378 (comment). Zoom in around timestamp 208,125 ms.
What did you expect to see?
All of the events in the visible time window, regardless of zoom.
What did you see instead?
When the zoom gets close enough to show a few milliseconds on the screen (it happens around 8 ms for me), the sweep events on proc 0 start to flicker, shift around, and disappear. If you keep zooming in, several of them will disappear entirely. You can tell that they should be there by clicking on one of the events that's still visible, pressing left or right a few times to navigate to a neighboring event, and then pressing 'm' to mark the duration of the selected event. If you're on one of the invisible events, it will highlight a range that appears to have nothing in it.
What version of Go are you using (
go version
)?go version go1.8 linux/amd64
What operating system and processor architecture are you using (
go env
)?What did you do?
Use
go tool trace
on the trace from #19378 (comment). Zoom in around timestamp 208,125 ms.What did you expect to see?
All of the events in the visible time window, regardless of zoom.
What did you see instead?
When the zoom gets close enough to show a few milliseconds on the screen (it happens around 8 ms for me), the sweep events on proc 0 start to flicker, shift around, and disappear. If you keep zooming in, several of them will disappear entirely. You can tell that they should be there by clicking on one of the events that's still visible, pressing left or right a few times to navigate to a neighboring event, and then pressing 'm' to mark the duration of the selected event. If you're on one of the invisible events, it will highlight a range that appears to have nothing in it.
Zoomed close but not too close:
Zoomed very slightly closer:
/cc @dvyukov
The text was updated successfully, but these errors were encountered: