We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
I have the following trace that gets rendered incorrectly in speedscope
[ { "name": "A", "ph": "X", "ts": 1732107141551429.079, "dur": 34670882.955, "pid": 1033891, "tid": 140390667650624, "args": {}}, { "name": "B", "ph": "X", "ts": 1732107142997066.682, "dur": 476375.838, "pid": 1033891, "tid": 140390667650624, "args": {}}, { "name": "C", "ph": "X", "ts": 1732107143473442.569, "dur": 300492.826, "pid": 1033891, "tid": 140390667650624, "args": {}} ]
The event B ends at 1732107143473442.520, and event C starts at 1732107143473442.569 (49ns later), so C should be on the same stack, but just after B.
1732107143473442.520
1732107143473442.569
However, this is how it gets visualized in speedscope:
And in perfetto.dev:
My hunch is that this could be due to a double precision issue.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi,
I have the following trace that gets rendered incorrectly in speedscope
The event B ends at
1732107143473442.520
, and event C starts at1732107143473442.569
(49ns later), so C should be on the same stack, but just after B.However, this is how it gets visualized in speedscope:
And in perfetto.dev:
My hunch is that this could be due to a double precision issue.
The text was updated successfully, but these errors were encountered: