1827186 - Google Meet leaking memory

Status: RESOLVED WORKSFORME

(Core :: Performance, defect)

Description

[Vsevolod Novikov]

Attachment: Several memory reports from the about:memory page

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

Steps to reproduce:

Open Google Meet and start a new meeting, or connect to an existing one

Actual results:

Memory consumption grows until the page is failed.

It's interesting, that when I try to save a report at about:memory while the Meet page is opened (and memory consumption grows), the report is not saved, but saved later after I close the Meet page.

Expected results:

Memory consumption increases and stabilizes at some level

Comment 1

[Vsevolod Novikov]

The application has been installed from the mozilla-flatpak 1.0 package

Comment 2

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

The Bugbug bot thinks this bug should belong to the 'Core::Performance' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 3

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

This bug was moved into the Performance component.

:nnseva, 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

[Vsevolod Novikov]

Attachment: about:support

Raw Info from the about:support

Comment 5

[Bas Schouten (:bas.schouten)]

Hrm. Sadly I don't see anything particularly shocking in these memory reports. Mccr8, did I miss something here?

Comment 6

[Andrew McCreight [:mccr8]]

The "during" page has around 830MB of shmem-allocated and shmem-mapped, and resident and resident unique values around 1GB. That's a bit high, but I'm not sure if that's unusual.

Unfortunately if a process is unresponsive due to being overloaded this can make the memory reporting not work very well either. Maybe that's an issue here.

Comment 7

[Andrew McCreight [:mccr8]]

I'll put a "see also" here to bug 1828587, as these are both about video using a lot of memory, but it looks like this report is from 111 so it probably isn't the same thing.

Comment 8

[Vsevolod Novikov]

Hi people,

I should sadly tell you, that after some number of days, the system libraries were updated, and the main issue (growing memory consumption) apparently looks like disappeared.

The only (minor?) issue which looks like remained on my host, is that the memory report is not created while the Google Meet page is open, but after closing it, the report appears to be generated on the memory:about page.

Comment 9

[Andrew McCreight [:mccr8]]

Yeah, that's very strange. I'll mark this as works-for-me. I'm glad your problem went away.