Chrome Tab Memory Bloat

[Müller, Sebastian]

Dear Chromium Team, 

I have an odd issue with a web app I am building. 

A user is experiencing huge Memory footprint in the tab of my app (sometimes >11 GB RAM) and corresponding terrible performance.

However, when analyzing this in his browser I saw that the JS Heap of our app is in the low hundreds of MB. So that seems to point away to my immediate thought of a memory leak on our side.

The rest of the RAM seems to be taken up by chrome itself.

I couldn't reproduce this issue on my machine. I told him to try Firefox and for now the issue hasn't reoccurred. 

For him, it's reproducible in Chrome though. 

Can you help me analyze it further? What data would you need and how can I collect it?


best regards,

Sebastian Müller

 

ASCon Systems Holding GmbH | Curiestraße 5 | 70563 Stuttgart

sebastia...@ascon-systems.de

Phone +49 711 2585890

www.ascon-systems.de | Social Media: LinkedIn, Xing, Facebook, Vimeo

 

Handelsregister Stuttgart HRB 722606, Geschäftsführer: Jens Müller, Uwe Reumuth

 

[Egor Pasko]

Hello Sebastian,

You can get more information about memory usage outside of JS heap from a "memory-infra" memory dump.

Here is documentation about memory-infra: https://chromium.googlesource.com/chromium/src/+/main/docs/memory-infra/

A number of the categories you will see in the report are somewhat cryptic. Sorry about that. If it turns out to be a browser issue, those memory dumps will help chromium developers find the root cause.

--
You received this message because you are subscribed to the Google Groups "memory-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to memory-dev+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/memory-dev/FR1PPF0F447044BD3E57AE13B81E0C5E9B3CEA42%40FR1PPF0F447044B.DEUP281.PROD.OUTLOOK.COM.

[Müller, Sebastian]

Hello Egor, 

thanks for the tip and the quick reply! 

I generated a trace where my tab had around 4.9 gigs of RAM. This seemed to correspond well with a Renderer process.

The two largest values there are by far  blink_gc with around 1.8 GB and malloc with around 2.5 GB. 

Does this point into the direction of a browser issue?

Let me know how to proceed. The file is unfortunately a bit large for an email extension.

best regards

Sebastian Müller

 

ASCon Systems Holding GmbH | Curiestraße 5 | 70563 Stuttgart

sebastia...@ascon-systems.de

Phone +49 711 2585890

www.ascon-systems.de | Social Media: LinkedIn, Xing, Facebook, Vimeo

 

Handelsregister Stuttgart HRB 722606, Geschäftsführer: Jens Müller, Uwe Reumuth

 

---

Von: Egor Pasko <pa...@chromium.org>
Gesendet: Montag, 24. März 2025 16:28
An: Müller, Sebastian <Sebastia...@ascon-systems.de>
Cc: memor...@chromium.org <memor...@chromium.org>
Betreff: [EXTERN] Re: Chrome Tab Memory Bloat

 

ACHTUNG: Diese E-Mail stammt von einem externen Absender. Bitte vermeide es, Anhänge oder externe Links zu öffnen.

[Egor Pasko]

Please 'minimize' the reproducer as much as possible and create a http://crbug.com issue with your (hopefully minimized) trace with the corresponding memory dump.

Generally large bling_gc and malloc heaps may indicate DOM manipulation issues or JS memory leaks, but a browser-side issue is also a possibility.

[Dominik Inführ]

+1 to what Egor already wrote.

I just want to add that you can make "special" heap snapshots from DevTools with a "chrome for testing" release which includes blink_gc (=cppgc) as well. See the documentation here: https://chromium.googlesource.com/chromium/src/+/lkgr/docs/memory/tools.md#dev-tools-heap-snapshots. If the leak is coming from blink_gc/the JS heap, this tool should help you figure out what is keeping objects/memory live.

Hope this helps and good luck!

On Monday, March 24, 2025 at 5:21:19 PM UTC+1 Egor Pasko wrote:

Please 'minimize' the reproducer as much as possible and create a http://crbug.com issue with your (hopefully minimized) trace with the corresponding memory dump.

Generally large bling_gc and malloc heaps may indicate DOM manipulation issues or JS memory leaks, but a browser-side issue is also a possibility.

On Mon, Mar 24, 2025 at 5:00 PM Müller, Sebastian <Sebastian.Mueller@ascon-systems.de> wrote:

Hello Egor, 

thanks for the tip and the quick reply! 

I generated a trace where my tab had around 4.9 gigs of RAM. This seemed to correspond well with a Renderer process.

The two largest values there are by far  blink_gc with around 1.8 GB and malloc with around 2.5 GB. 

Does this point into the direction of a browser issue?

Let me know how to proceed. The file is unfortunately a bit large for an email extension.

best regards

Sebastian Müller

 

ASCon Systems Holding GmbH | Curiestraße 5 | 70563 Stuttgart

sebastian.mueller@ascon-systems.de

Phone +49 711 2585890

www.ascon-systems.de | Social Media: LinkedIn, Xing, Facebook, Vimeo

 

Handelsregister Stuttgart HRB 722606, Geschäftsführer: Jens Müller, Uwe Reumuth

 

Von: Egor Pasko <pa...@chromium.org>
Gesendet: Montag, 24. März 2025 16:28

An: Müller, Sebastian <Sebastian.Mueller@ascon-systems.de>

Cc: memor...@chromium.org <memor...@chromium.org>
Betreff: [EXTERN] Re: Chrome Tab Memory Bloat

ACHTUNG: Diese E-Mail stammt von einem externen Absender. Bitte vermeide es, Anhänge oder externe Links zu öffnen.

Hello Sebastian,

You can get more information about memory usage outside of JS heap from a "memory-infra" memory dump.

Here is documentation about memory-infra: https://chromium.googlesource.com/chromium/src/+/main/docs/memory-infra/

A number of the categories you will see in the report are somewhat cryptic. Sorry about that. If it turns out to be a browser issue, those memory dumps will help chromium developers find the root cause.

On Mon, Mar 24, 2025 at 9:24 AM Müller, Sebastian <Sebastian.Mueller@ascon-systems.de> wrote:

Dear Chromium Team, 

I have an odd issue with a web app I am building. 

A user is experiencing huge Memory footprint in the tab of my app (sometimes >11 GB RAM) and corresponding terrible performance.

However, when analyzing this in his browser I saw that the JS Heap of our app is in the low hundreds of MB. So that seems to point away to my immediate thought of a memory leak on our side.

The rest of the RAM seems to be taken up by chrome itself.

I couldn't reproduce this issue on my machine. I told him to try Firefox and for now the issue hasn't reoccurred. 

For him, it's reproducible in Chrome though. 

Can you help me analyze it further? What data would you need and how can I collect it?


best regards,

Sebastian Müller

 

ASCon Systems Holding GmbH | Curiestraße 5 | 70563 Stuttgart

sebastian.mueller@ascon-systems.de

Phone +49 711 2585890

www.ascon-systems.de | Social Media: LinkedIn, Xing, Facebook, Vimeo

 

Handelsregister Stuttgart HRB 722606, Geschäftsführer: Jens Müller, Uwe Reumuth

 

--
You received this message because you are subscribed to the Google Groups "memory-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to memory-dev+unsubscribe@chromium.org.