New issue
Advanced search Search tips

Issue 719459 link

Starred by 3 users

Issue metadata

Status: Duplicate
Merged: issue 610832
Owner: ----
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Closing all windows for a profile does not tear down the profile object

Project Member Reported by wjmaclean@chromium.org, May 8 2017

Issue description

Chrome Version: 58.0.3029.81
OS: Observed on Linuix, but I'm guessing all

What steps will reproduce the problem?
(1) open two profiles in chrome, each with extensions
(2) close all the windows of one profile
(3) investigate with task manager

What is the expected result?

There should be no processes left that are associated with the 'closed' profile.

What happens instead?

Background pages for the closed profile are still there.

Please use labels and text to provide additional information.

I think that most users, when closing a profile on a particular machine, don't expect there to still be account activity when they've closed all the windows, and would not expect to have to open task manager to kill off the extension background pages.

 
Cc: lazyboy@chromium.org
The root cause of this is that we don't tear down profiles, ever.  Extensions are tied to a profile, but if we don't collect that object, everything is left around.  Solving this as a one-off for extensions is likely the wrong solution.

This is somewhat related to issue 130656... lazyboy@, is there a bug that more accurately encompasses closing browser windows not closing the profile?
I just wanted to report this very much. Especially annoying on a laptop with small RAM (extensions from closed profile's browser take up much RAM and I have to kill them manually)
Cc: rdevlin....@chromium.org
Components: -Platform>Extensions UI>Browser>Profiles
Owner: ----
Summary: Closing all windows for a profile does not tear down the profile object (was: Closing all windows for a profile does not close associated extension background pages)
Updating the description to more accurately match the bug.  If we actually destroy the profile, then extensions should be collected along with it.
Related (and possibly just dupe): issue 610832

I'll leave it up to the profiles team what they wanna do here.
Mergedinto: 610832
Status: Duplicate (was: Untriaged)
Thanks, Devlin! Closing this one as a duplicate.

Sign in to add a comment