Closed Bug 1804655 Opened 1 year ago Closed 1 year ago

high cpu usage and memory when using the JSON viewer on an 8MB file

Categories

(DevTools :: JSON Viewer, defect, P3)

Firefox 107
Desktop
macOS
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1363222

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.

Attached file md5sum.json

The 10 MB API response that I was trying to view in the new tab

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.

Severity: -- → S3
Status: UNCONFIRMED → NEW
Component: Untriaged → DOM: Content Processes
Ever confirmed: true
OS: Unspecified → macOS
Product: Firefox → Core
Hardware: Unspecified → Desktop
Severity: S3 → --
Component: DOM: Content Processes → JSON Viewer
Product: Core → DevTools

I'll make the summary more specific so it doesn't draw in comments from people with unrelated performance issues.

Summary: firefoxCP Isolated Webcontent process high cpu usage and memory → high cpu usage and memory when using the JSON viewer on an 8MB file
Attachment #9307286 - Attachment mime type: text/plain → application/json

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.

Severity: -- → S3
Priority: -- → P3

Can we combine this with bug 1363222?

Flags: needinfo?(odvarko)

Yes, agree.

Status: NEW → RESOLVED
Closed: 1 year ago
Duplicate of bug: 1363222
Flags: needinfo?(odvarko)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: