Open
Bug 1330633
(ss-reliability)
Opened 7 years ago
Updated 2 months ago
[meta] Sessionstore reliability tracking
Categories
(Firefox :: Session Restore, defect)
Tracking
()
NEW
People
(Reporter: mikedeboer, Unassigned)
References
(Depends on 96 open bugs)
Details
(Keywords: meta)
We set three tiers that we’ll use to theme and prioritize sessionstore component work: Tier 1: Reliability Tier 2: Performance Tier 3: Feature development and maintenance We agreed that Tier 1 is something that will be a theme throughout the year, overlapping in some areas with Tier 2 (please read on for more details): main parts being telemetry monitoring and bug triage focused on that category. Action points: 1. Setup a telemetry dashboard that gives insight into the data we’re already collecting - we already have more than 20 probes, but no real grasp on coverage and/ or missing data 2. Help investigate and fix bugs filed regarding ‘missing tabs’, ‘missing windows’ or failed restores. Bugs which have 'reliability' as its main theme will be marked blocking this bug.
Reporter | ||
Updated•7 years ago
|
Depends on: eternalsession
Updated•7 years ago
|
Reporter | ||
Updated•7 years ago
|
Comment 1•7 years ago
|
||
I don’t have privs to add dependencies, but https://bugzilla.mozilla.org/show_bug.cgi?id=539597 is a candidate.
Updated•6 years ago
|
Updated•6 years ago
|
Meta-bug for session managers: https://bugzilla.mozilla.org/show_bug.cgi?id=1427928
Updated•6 years ago
|
Updated•6 years ago
|
See Also: → ss-feature
See Also: → Session_managers, ss-perf
Updated•5 years ago
|
Summary: Sessionstore reliability tracking → [meta] Sessionstore reliability tracking
See Also: → tab-unloading
Updated•4 years ago
|
See Also: tab-unloading →
Updated•2 years ago
|
Severity: normal → S3
You should add a dependence for bug 1096726, bug 1201111, bug 1343402, bug 1413315, bug 1631101, bug 1675743, bug 1681015, bug 1688467, bug 1775100, bug 1777446, bug 1785779, bug 1790271, bug 1803710, bug 1803997, bug 1808407 and bug 1827994.
FWIW only the sixth last has any really actionable info, but I think one easy picking could be starting to look into why large sessions can so comfortably and elusively break tracking/storage on x86.
You need to log in
before you can comment on or make changes to this bug.
Description
•