Google Chrome Helper using High amounts of RAM on OS X

[Martin Ritchie]

I've had a search on here and in the bug tracker but not seeing anything that seems to cover what I'm seeming.

My Mac this morning was showing ALL the ram being used by a Google Chrome Helper, that is 16Gb in one process!

I'm running OS X 10.11.3

and

Chrome 48.0.2564.97

All I could find is this was:

chat around "DYLD shared region unnest for map" that might be showing increases in memory but was marked as harmless:

https://code.google.com/p/chromium/issues/detail?id=428858

and this one about High Ram usage but it is focused on the discrepancy between Chrome memory reporting and Activity Monitor.

https://code.google.com/p/chromium/issues/detail?id=439343

I don't mind the Chrome memory readings being wrong, which looks to be why this issue was closed. Though it does say some memory fixes have been included in Chrome 46 but given I'm running 48 I'd say there is something else up.

Does anyone have any ideas what might be going on or how I can prevent this happening?

Cheers

Martin

[Philip Rogers]

Possibly an extension gone awry? Can you try disabling extensions in chrome://extensions ?

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

---
You received this message because you are subscribed to the Google Groups "Chromium-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discu...@chromium.org.

[Primiano Tucci]

Can you please grab a trace following the doc below, file a bug, CC me (or just post the link here) and attach the trace .json.gz to the bug?

https://chromium.googlesource.com/chromium/src/+/master/components/tracing/docs/memory_infra.md

It looks like there is something weird going on there.

If you can grab a trace that would really a lot.

Thanks for reaching out

[Primiano Tucci]

[this time from the right address, apologies if you received this message twice]

Can you please grab a trace following the doc below, file a bug, CC me (or just post the link here) and attach the trace .json.gz to the bug?

https://chromium.googlesource.com/chromium/src/+/master/components/tracing/docs/memory_infra.md

It looks like there is something weird going on there.

If you can grab a trace that would really a lot.

Thanks for reaching out

On Sun, Jan 31, 2016 at 8:57 PM Philip Rogers <p...@chromium.org> wrote:

[Martin Ritchie]

Hey guys,

Thanks for the reply, Always happy to help so will disable the few extensions I have and get a memory trace when/if it next occurs. 

Unless you think a memory dump after closing the 16G process would be interesting.

Cheers

Martin

[Primiano Tucci]

It would be great to get the memory dump when the 16 GB issue happens.

Do NOT disable the extensions that you think cause the issue, otherwise we won't be able to tell which one caused the issue :)

In other words, I'd like to see the 16GB there somewhere when you capture the trace.

[Martin Ritchie]

That makes sense. If it is a plugin then we'd be waiting a while for it to take all the ram again :)

Ok will let you know when it goes crazy.

Cheers

Martin

[Sophia Dwyer]

I figured it out. It was eating up over 300% of my mac's memory and making my computer heat up like an oven even though I've only had it for a few months. To solve this I opened Activity Manager (located in the utilities folder in the applications), and control-clicked on the google chrome helper until I got a window (had to double click). At the bottom of the window there was a quit button and I clicked it and it closed it out and my chrome still works fine.