high cpu usage and memory when using the JSON viewer on an 8MB file
Categories
(DevTools :: JSON Viewer, defect, P3)
Tracking
(Not tracked)
People
(Reporter: muratkerimaslan, Unassigned)
Details
Attachments
(4 files)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:107.0) Gecko/20100101 Firefox/107.0
Steps to reproduce:
Opened firefox and went to "10.3.2.13:8080/database/md5sum", to see the JSON result of an API, the result is a 10 MB JSON. (Attached)
Actual results:
CPU usage of "FirefoxCP Isolated Webcontent" process, went up to 100%, and its memory usage went up 10GB in activity monitor.
Expected results:
I expected to view JSON content in either expandable tabs, or RAW JSON, but the page was unresponsive.
Reporter | ||
Comment 1•1 year ago
|
||
The 10 MB API response that I was trying to view in the new tab
Reporter | ||
Comment 2•1 year ago
|
||
Reporter | ||
Comment 3•1 year ago
|
||
Comment 4•1 year ago
|
||
I was able to reproduce this issue in all versions of Firefox from Esr to our latest Nightly build.
I saved the file locally and after loading it into Firefox the CPU would jump to 103% and drop back to 101%.
I will change the component to Core Dom: Content Process but I'm not entirely sure its the correct one, maybe one of our devs can take a look at the memory report and they can move it to the correct component, there is a handful of similar bugs related the FirefoxCP and im not sure if its a duplicate for any of them.
Updated•1 year ago
|
Comment 5•1 year ago
|
||
I'll make the summary more specific so it doesn't draw in comments from people with unrelated performance issues.
Updated•1 year ago
|
Comment 6•1 year ago
|
||
One option is to bail out from the json viewer and use the raw view if the size exceeds a certain limit, but we should still investigate the performance issue and see if there are obvious improvements to do.
Yes, agree.
Updated•1 year ago
|
Description
•