New issue
Advanced search Search tips

Issue 751468 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 491430
Owner: ----
Closed: Aug 2017
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Extensions, running when opening users profiles, not terminated when closing users profiles

Reported by berkut.u...@gmail.com, Aug 2 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.78 Safari/537.36

Steps to reproduce the problem:
1. Run browser. Result: shown first window with first user profile.
2. Open second window with second user profile. Result: shown first window for first user profile and second window for second user profile.
3. Close first window. Result: shown second window for second user profile.
4. Open third window with third user profile. Result: shown second window for second user profile and third window for third user profile.
5. Close second window. Result: shown third window for third user profile.
6. Open four window with four user profile. Result: shown third window for third user profile and four window for four user profile.
7. Close third window. Result: shown four window for four user profile.
Current state: opened four window with four user profile; extensions of first, second, third and four profiles are running.
If user open new window with first profile, will be used already running extensions of first profile.

What is the expected behavior?
Expected behavior: after closing last window of user profile, all extensions of user profile must be terminated; extensions of user profile must not be running, if all windows of user profile are closed; after open window with other user profile, other user profile extensions must be running again.

What went wrong?
Not used and still running extension consume resources.

Did this work before? N/A 

Chrome version: 60.0.3112.78  Channel: stable
OS Version: 
Flash Version:
 

Comment 1 by woxxom@gmail.com, Aug 2 2017

Duplicate of issue 491430
Mergedinto: 491430
Status: Duplicate (was: Unconfirmed)
The issue looks similar to issue id: 491430. Hence, merging into issue id: 491430.
Please feel free to undupe if not the case.

Thanks...!!

Sign in to add a comment