Open Bug 1549807 Opened 5 years ago Updated 2 years ago

[meta] Way too much heap-unclassified memory allocated in the main process

Categories

(Core :: General, defect, P3)

defect

Tracking

()

Tracking Status
firefox68 --- affected

People

(Reporter: bzbarsky, Unassigned)

References

(Depends on 3 open bugs)

Details

(Keywords: meta)

Attachments

(3 files)

Attached file log.txt

I am currently looking at about 1.3GB heap-unclassified in my main browser process after browsing for a couple of weeks. DMD log attached; I will be following up with analysis and some bugs on parts of this log...

General breakdown of the heap-unclassified:

  1. 242MB no stack trace recorded due to --stacks=partial
  2. Over 740MB gfx bits. Bug 1549819.
  3. 113MB stuff hanging off NSEvents? Bug 1491068 probably relevant.

The rest is all fairly small...

Depends on: 1549819, 1491068

The priority flag is not set for this bug.
:nhi, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(nhnguyen)

This bug doesn't look specifically like a networking issue. Wrong ni? perhaps?

Flags: needinfo?(nhnguyen) → needinfo?(sledru)
Flags: needinfo?(sledru)

The priority flag is not set for this bug.
:nhi, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(nhnguyen)
Flags: needinfo?(nhnguyen)
Priority: -- → P3
Summary: Way too much heap-unclassified memory allocated in the main process → [meta] Way too much heap-unclassified memory allocated in the main process
Depends on: 1590632
Depends on: 1625262
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: