Skip to content
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 Chrome Trace Event profile #4915

Open
ilyapopov opened this issue Feb 10, 2024 · 1 comment
Open

Cannot open Chrome Trace Event profile #4915

ilyapopov opened this issue Feb 10, 2024 · 1 comment

Comments

@ilyapopov
Copy link

ilyapopov commented Feb 10, 2024

This file cannot be loaded into firefox profiler. To my knowledge, it conforms to the Chrome Trace Event format as specified by Google's documentation. Ref: https://docs.google.com/document/d/1CvAClvFfyA5R-PhYUmn5OOQtYMH4h6I0nSsKchNAySU/preview

[
{"name": "Initialization", "cat": "", "ph": "X", "pid": 346905, "tid": 346905, "ts": 2343, "dur": 100}
]

The error message is:

Error: Unserializing the profile failed: Error: This does not appear to be a valid Gecko Profile, there is no meta field.

In fact, Firefox profiler cannot even open the file shown in that document as an example:

[ {"name": "Asub", "cat": "PERF", "ph": "B", "pid": 22630, "tid": 22630, "ts": 829},
  {"name": "Asub", "cat": "PERF", "ph": "E", "pid": 22630, "tid": 22630, "ts": 833} ]

The same file can be opened fine by other tools that support Trace Events format.

┆Issue is synchronized with this Jira Task

@mstange
Copy link
Contributor

mstange commented Feb 10, 2024

The Chrome format importer currently handles profiles exported from the Performance panel in the Chrome devtools - those profiles have sample and stack data.
The importer currently does not handle the generic Chrome Trace Event format. But it would be nice if it did!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants