Closed
Bug 1358735
Opened 7 years ago
Closed 7 years ago
Container tabs are intermittently not restored in a container
Categories
(Firefox :: Session Restore, defect)
Firefox
Session Restore
Tracking
()
VERIFIED
FIXED
Firefox 55
Tracking | Status | |
---|---|---|
firefox55 | --- | verified |
People
(Reporter: marco, Assigned: u462496)
References
Details
Attachments
(1 file)
1.14 KB,
patch
|
mikedeboer
:
review+
|
Details | Diff | Splinter Review |
I'm seeing this intermittently. After a session restore, some tabs lose the container information and are restored in the default container instead of the container they are supposed to be in.
(In reply to Marco Castelluccio [:marco] from comment #0) > I'm seeing this intermittently. After a session restore, some tabs lose the > container information and are restored in the default container instead of > the container they are supposed to be in. Hi Marco, I am not following you when you speak of "containers". Can you give more details?
Comment 2•7 years ago
|
||
I can reproduce the problem. Reproducible : always Steps To Reproduce: 1. Set "When Firefox starts" to "Show my windows and tabs from last time" 2. Open 3 tabs (for example) tab 1: [about:home] personal container tab1 2: [https://developer.mozilla.org/en-US/Add-ons/WebExtensions] personal container tab1 3: [https://developer.mozilla.org/en-US/Add-ons/WebExtensions] 3. Restart browser twice Actual Results: the container tab unexpectedly changes to normal tab. Expected Results: the container tab should be restored as before
(In reply to Alice0775 White from comment #2) > I can reproduce the problem. > > Reproducible : always > > Steps To Reproduce: > 1. Set "When Firefox starts" to "Show my windows and tabs from last time" > 2. Open 3 tabs (for example) > tab 1: [about:home] > personal container tab1 2: > [https://developer.mozilla.org/en-US/Add-ons/WebExtensions] > personal container tab1 3: > [https://developer.mozilla.org/en-US/Add-ons/WebExtensions] > 3. Restart browser twice > > Actual Results: > the container tab unexpectedly changes to normal tab. > > Expected Results: > the container tab should be restored as before If you set `browser.sessionstore.restore_tabs_lazily` to false, do you still get this behavior?
Comment 4•7 years ago
|
||
(In reply to Kevin Jones from comment #3) > > If you set `browser.sessionstore.restore_tabs_lazily` to false, do you still > get this behavior? When set `browser.sessionstore.restore_tabs_lazily` to false, the problem dos not occur. It works as expected.
I am seeing that if the browser is restarted while the container tabs have been restored, they will remain intact. It is when the browser has been shut down but the tabs have never been restored for that session, that the next time the browser starts, they lose their container identity. Can anyone tell me where to find the API which manages container tabs or how their data is persisted? I do not find any clues in sessionstore.js.
Comment 6•7 years ago
|
||
If you want to learn more about containers, start here: https://wiki.mozilla.org/Security/Contextual_Identity_Project/Containers An interesting question is if this issue manifests itself with the Test Pilot add-on or just the container implementation in Nightly: https://testpilot.firefox.com/experiments/containers
Comment 7•7 years ago
|
||
I confirm that tab lazy loading is the problem as it doesn't affect pinned tabs (that are now lazy loaded AFAIK).
userContextId doesn't get set in TabStateCache if the lazy tab never gets fully restored. This patch assures it gets set during window restore.
Attachment #8861372 -
Flags: review?(mdeboer)
Comment 9•7 years ago
|
||
Comment on attachment 8861372 [details] [diff] [review] 1358735_patch_ensure_userContextId_always_set_in_TabStateCache_V1.diff Review of attachment 8861372 [details] [diff] [review]: ----------------------------------------------------------------- Ah! makes sense.
Attachment #8861372 -
Flags: review?(mdeboer) → review+
Updated•7 years ago
|
Assignee: nobody → kevinhowjones
Status: NEW → ASSIGNED
Updated•7 years ago
|
Keywords: checkin-needed
Comment 11•7 years ago
|
||
Pushed by ryanvm@gmail.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/91188e528813 Ensure userContextId is always set in TabStateCache. r=mikedeboer
Keywords: checkin-needed
Updated•7 years ago
|
Flags: needinfo?(mdeboer)
Comment 12•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/91188e528813
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
status-firefox55:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 55
Comment 13•7 years ago
|
||
I have reproduced this on Firefox Nightly according to (2017-04-22) Fixing bug is verified on Latest Nightly--Build ID : (20170430030208),User Agent: Mozilla/5.0 (Windows NT 6.1; rv:55.0) Gecko/20100101 Firefox/55.0 Tested OS-- Windows7 32bit [bugday-20170426]
Updated•7 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•