1878896 - Randomly occurring memory leak

Status: RESOLVED INVALID

(Core :: Performance: General, defect)

Description

[git]

Attachment: memory-report.json.gz

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:122.0) Gecko/20100101 Firefox/122.0

Steps to reproduce:

I have no way of reproducing this issue, it seems to be entirely random from my perspective.

Actual results:

Firefox uses up a lot of ram (>20 gigabytes) and the usage keeps increasing at a rate of about 100 megabytes per second until I either run out of memory entirely or the increasing stop and the memory usage quickly drops down back to normal.

Expected results:

My normal total system memory usage hovered around 8-9 gigabytes with the 50 tabs I had open, most of which were suspended.

Comment 1

[git]

Attachment: troubleshooting_information.json

Comment 2

[git]

The memory report might not contain information about the leak, because the memory usage dropped quite quickly when I was saving the report.

I will be attaching new memory reports when I come across this leak again.

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

This bug was moved into the Performance component.

:git, could you make sure the following information is on this bug?

• For slowness or high CPU usage, capture a profile with http://profiler.firefox.com/, upload it and share the link here.
• ✅ For memory usage issues, capture a memory dump from about:memory and attach it to this bug.
• ~~✅ Troubleshooting information: Go to about:support, click "Copy raw data to clipboard", paste it into a file, save it, and attach the file here.
  ~~

If the requested information is already in the bug, please confirm it is recent.

Thank you.

Comment 4

[git]

I have attached a memory report and the troubleshooting information from about:support, however I'm unsure if the memory report contains the information required, since the leak is very time sensitivve.

I also can't really capture a profile unless it is appropriate to keep the profiler running for very long periods of time.

Currently I have no way of reproducing the memory leak in a reliable way and thus have to simply wait for it to happen. I will be submitting a new memory report here when I manage to get one in time.

Comment 5

[git]

Almost two weeks has passed and I haven't had this memory leak reoccur and I'm beginning to suspect that this was possibly caused by badly written javascript on some website I had open in the background. I have had some tabs use up lots of CPU resources after waking my system from sleep, but that's probably unrelated to this issue since those tabs only used lots of CPU resources but not RAM.

Comment 6

[Julien Wajsberg [:julienw]]

Interesting, thanks for reporting!
I'll go ahead and close this bug then, but please file a new bug with all the information if you see this again!