-
Notifications
You must be signed in to change notification settings - Fork 330
New issue
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
Cannot open some perfetto trace files in v45 (But works in v44) #818
Comments
@benny8453123 Can you please attach a trace? Otherwise it's impossible to act on this |
This was fixed in https://r.android.com/3063482. Please use canary/autopush for now, we should be doing a stable release soon! |
I think @stevegolton actually just did a stable release soon. Maybe we should cherry-pick the fix on stable then? |
https://r.android.com/3125096 will fix the issue on autopush. Agree we should cherry-pick these patches on stable. |
There are platform bugs which cause massive (unreasonble) timestamps in frame timeline: simply drop them. This is similar to b/185978397 but it's a different bug Bug: #818 Change-Id: Ib96479a8bd9a3bf045c232edf834ec338a2d3ba0
I tried the autopush version today, and Perfetto can now work with the previous trace file normally. |
There are platform bugs which cause massive (unreasonble) timestamps in frame timeline: simply drop them. This is similar to b/185978397 but it's a different bug Bug: google/perfetto#818 Change-Id: Ib96479a8bd9a3bf045c232edf834ec338a2d3ba0
There are platform bugs which cause massive (unreasonble) timestamps in frame timeline: simply drop them. This is similar to b/185978397 but it's a different bug Bug: google/perfetto#818 Change-Id: Ib96479a8bd9a3bf045c232edf834ec338a2d3ba0
I've pushed this to stable now so closing this out. |
Hi,
Since last Firday I cannot open some perfetto trace files. The error was shown below:
And I found there is upgrade was published at last Firday (Jun 07 6:02 PM) (according to perfetto/ui/release/channels.json)
How can I fix it or downgrade to v44 version in Windows platform?
The text was updated successfully, but these errors were encountered: