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
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.
The text was updated successfully, but these errors were encountered:
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.
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.
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.
The text was updated successfully, but these errors were encountered: