Open
Bug 1438248
Opened 6 years ago
Updated 1 year ago
First two pinned tabs switch places sometimes after startup
Categories
(Firefox :: Session Restore, defect, P5)
Firefox
Session Restore
Tracking
()
NEW
People
(Reporter: dietrich, Unassigned)
References
(Blocks 1 open bug)
Details
60.0a1 (2018-02-13) (64-bit) Mac OS X I've usually got 4-5 pinned tabs, configured to always restore session. I have noticed repeatedly that after startup the first two pinned tabs (left-most) have switched places. No other pinned tabs or other tabs are different at all, that I've ever seen. Sadly, I have no other repro steps than that. But it's happened enough times that I think it is worth reporting. I'm going to disable the few add-ons I use before my daily restarts for the Nightly update, and see if maybe this is caused by one of them. If it *is* add-on caused by an add-on, we might need to look at how add-ons can impact session restoration, and mitigate issues from things like non-deterministic timing of add-on loading.
Comment 1•6 years ago
|
||
Hi Dietrich, were you able to figure out whether this was caused by an addon after all? Otherwise, since I haven't seen this myself, I'll have to close this as WFM. Thanks!
Flags: needinfo?(dietrich)
Updated•6 years ago
|
Blocks: ss-reliability
Priority: -- → P5
Reporter | ||
Comment 2•6 years ago
|
||
I don't know. It happens rarely and unpredictably. I lived without the addons for about a week, but I don't remember if it happened then or not :(
Flags: needinfo?(dietrich)
Updated•2 years ago
|
Severity: normal → S3
Comment 3•2 years ago
|
||
The severity field for this bug is relatively low, S3. However, the bug has 11 votes.
:dao, could you consider increasing the bug severity?
For more information, please visit auto_nag documentation.
Flags: needinfo?(dao+bmo)
Comment 4•2 years ago
|
||
The last needinfo from me was triggered in error by recent activity on the bug. I'm clearing the needinfo since this is a very old bug and I don't know if it's still relevant.
Flags: needinfo?(dao+bmo)
You need to log in
before you can comment on or make changes to this bug.
Description
•