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

Issue 718980 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
ssid@chromium.org
█ mariakho...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Opening a site via NTP uses more memory in the browser process

Project Member Reported by dskiba@chromium.org, May 5 2017 
Opening a site via a shortcut results in less dirty / PSS memory in the browser process vs opening the same site via NTP.

NTP:
* PSS: 56.8 MiB, private dirty: 27.4 MiB
* PSS: 56.3 MiB, private dirty: 27.5 MiB
* PSS: 56.5 MiB, private dirty: 27.5 MiB

Shortcut:
* PSS: 54.4 MiB, private dirty: 26.8 MiB
* PSS: 53.1 MiB, private dirty: 25.5 MiB
* PSS: 53.8 MiB, private dirty: 26.0 MiB


Unfortunately, the difference doesn't seem to be actionable from the Chrome side, it looks like that in NTP case Android dirties more memory. Plus more code is touched, resulting in more PSS.
shortcut-n-1.json.gz
450 KB Download
shortcut-n-2.json.gz
452 KB Download
shortcut-n-3.json.gz
449 KB Download
ntp-n-1.json.gz
459 KB Download
ntp-n-2.json.gz
457 KB Download
ntp-n-3.json.gz
458 KB Download

Comment 1 by dskiba@chromium.org, May 5 2017

Cc: ssid@chromium.org

Comment 2 by mariakho...@chromium.org, May 8 2017 

Hmm, have you tried comparing to a page opened via an intent? I wonder if shortcut goes through an entirely different code path.

Comment 3 by benhenry@chromium.org, May 8 2017

Labels: Performance-Memory

Comment 4 by benhenry@chromium.org, May 8 2017 

This might be the same as  crbug.com/707136

Comment 5 by erikc...@chromium.org, Jun 20 2017

Labels: Needs-Investigation
Status: Available (was: Untriaged)
Project Member

Comment 6 by sheriffbot@chromium.org, Jun 21 2018

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
►

Sign in to add a comment