Skip to content

Firefox profile unable to process profile #23

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

Open
akozhin-yint opened this issue Feb 17, 2025 · 2 comments
Open

Firefox profile unable to process profile #23

akozhin-yint opened this issue Feb 17, 2025 · 2 comments
Labels
wontfix This will not be worked on

Comments

@akozhin-yint
Copy link

Firefox profiler is unable to open json file. I am not sure if it is related to the size of profile. ELF file took around 7GB, .elfx 10GB. Final .json.gz is about 70MB. Unfortunately, cannot provide it.

I have run it on Release mode build, but I don't think it should be any problem.

Image

Image

@xoofx xoofx added the wontfix This will not be worked on label Feb 17, 2025
@xoofx
Copy link
Owner

xoofx commented Feb 17, 2025

Similar to #5

Unfortunately, I cannot fix it as it seems a limitation of the browser/library/frontend being used. I haven't investigated to see if it could be fixed.

@mstange
Copy link

mstange commented Feb 17, 2025

If you gzip decompress it, how big is the .json file?

Different browsers have different size limitations. For example, I think Firefox allows larger strings than Chrome, and one of the reasons for that is that Firefox doesn't use pointer compression. So you could try and see if the profile loads in Firefox.

Longer term I am working towards a binary format so that the front-end can use typed arrays everywhere, which are allowed to be much larger than strings or regular JS arrays.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants