New issue
Advanced search Search tips

Issue 688712 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 3
Type: Feature



Sign in to add a comment

Chrome Web Store: show extension memory footprint in the install confirmation dialog

Reported by woxxom@gmail.com, Feb 4 2017

Issue description

This is a feature suggestion for the dialog displayed by Chrome Web Store after users press "Add to Chrome" button (see the attached screenshot).

Since 1) many extensions add lots of code into *every* page by injecting content scripts, and 2) many users open lots of tabs (100+), it'd be good if Chrome Web Store displayed the size of injected code and the added memory footprint estimate based on the typical code-size-to-runtime-environment-size ratio.

I believe this will motivate extension authors to avoid injecting jQuery and other big JavaScript frameworks into *every* page instead of using plain JavaScript code. The end result will be faster loading of pages (since content script injection takes time), less overall memory usage for Chrome, and consequently better performance.
 
dialog.png
5.6 KB View Download

Comment 1 by woxxom@gmail.com, Feb 4 2017

Correction: the dialog is displayed by Chrome itself. So the feature request additionally applies to an inline installation of extensions, on-update permission change confirmation, local installations.
Labels: -Type-Bug Needs-Milestone OS-Linux OS-Mac OS-Windows Type-Feature
Status: Untriaged (was: Unconfirmed)
Thanks for the report. Considering this as Feature request and marking as Untriaged.

Requesting Dev team to check the issue and update accordingly.
Labels: -Needs-Milestone M-59
Components: Platform>Extensions
Cc: rdevlin....@chromium.org jawag@chromium.org
Labels: -M-59 OS-Chrome
Status: Available (was: Untriaged)
We'd love to be able to do something like this, but the first step is being able to accurately make an estimate of extension memory usage - which is itself very difficult.  We're pursuing a few different approaches in this area, though, and definitely agree that extension resource consumption is a common problem.
Project Member

Comment 6 by sheriffbot@chromium.org, Nov 12

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: Available (was: Untriaged)

Sign in to add a comment