New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 712730 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner: ----
Closed: Aug 22
Cc:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

macOS system runs out of memory.

Project Member Reported by erikc...@chromium.org, Apr 18 2017

Issue description

"""
Hahaha yes O.o  MacOS suspended chrome and gave me the "Your device ran out of memory! Please terminate one of the following programs:"

Choices were textmate, terminal, and chrome (suspended)
...
I killed everything else except chrome, and it still said it's out of memory, so I killed chrome and restarted it.
"""

I've attached the activity monitor screenshot and memory-infra trace.
 
chili_trace_filtered.json.gz
4.1 MB Download
chili_screenshot.png
446 KB View Download
Cc: xunji...@chromium.org
There are at least two problems:
1) Wired memory is at 5GB. macOS seems to run into issues when wired memory hits ~1/3 of total memory.
2) Browser process malloc is >1GB. We do have a net MemoryDumpProvider, but it doesn't have all the fields I expect.

xunjieli: Is there any way we can tell if this is the same net leak in the browser process?
Re#1: Net/ MemoryDumpProvider looks fine. It's not related to  Issue 700617 .
SSL session cache (ssl_session_cache) has ~200 certs which is a normal number.
Http2 session pools (spdy_session_pool) look normal as well.
There were 8 live url requests from the main profile, which is a small number of requests. SDCH dictionaries (sdch_manager) took up most of the memory from net stack (1.7MiB). SDCH is being deprecated in  Issue 696815 .
Labels: Needs-Investigation
Status: Available (was: Untriaged)
Project Member

Comment 5 by sheriffbot@chromium.org, Aug 22

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: Fixed (was: Untriaged)
We've fixed several instances of both of these problems in the last year. Marking as fixed.

Sign in to add a comment