[meta] The War on Storage Initialization Failures

NEW
Unassigned

Status

()

defect
P2
normal
10 months ago
a month ago

People

(Reporter: janv, Unassigned)

Tracking

(Depends on 9 bugs, Blocks 1 bug, {meta})

Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox63 affected)

Details

Reporter

Description

10 months ago
No description provided.
Reporter

Updated

10 months ago
Depends on: 1423917
Reporter

Updated

10 months ago
Depends on: 1395102
Reporter

Updated

10 months ago
Depends on: 1422456
Reporter

Updated

10 months ago
Depends on: 1348705
Reporter

Updated

10 months ago
Depends on: 1436128
Reporter

Updated

10 months ago
Depends on: 1436188
Reporter

Updated

10 months ago
Depends on: 1425146
Reporter

Updated

10 months ago
Depends on: 1345585
Reporter

Updated

10 months ago
Depends on: 1395133

Updated

10 months ago
Depends on: 1482812

Updated

10 months ago
Priority: -- → P2
Reporter

Updated

10 months ago
Depends on: 1481716

Updated

10 months ago
Keywords: meta
Summary: The War on Storage Initialization Failures → The War on Storage Initialization Failures [meta]
Reporter

Updated

10 months ago
Duplicate of this bug: 1426119
Reporter

Updated

9 months ago
Depends on: 944918

Updated

9 months ago
Blocks: 1487479
Depends on: 1487779
See Also: → 1471375
Depends on: 1493262
Reporter

Updated

7 months ago
Depends on: 1491637
Status of this project this week:

[1] I plan to finish patches in bug 1423917 and send them to review this week and they should cover:
- A minor QuotaManager upgrade (mainly for cleaning obsolete origins)
  - Obsolete origins:
    - about+xxx+number (was found in bug 1422456)
    - Whitelist ".*", "desktop.ini", "Desktop.ini", and "Thumbs.db" (was reported in bug 1493262, bug 1423917, bug 944918)
    - Recognize chrome protocol
    - Ignore invalid origins during ungrades

[2] Since it's are hard to identify all the issues that affecting QM initializing, we should see the result after finishing bug 1436188 and its followup (bug 1487779).

I haven't carefully checked about bug 1436128, bug 1395133, bug 1348705, and bug 1267349, but I don't think they affects many users. Will take care of them after completing [1] and [2].
Add the bug for having a nicer error message when indexedDB finds an unexpected file in the indexedDB directory.
Depends on: 1502077
Status of this project this week:

1. Most patches in the bug 1423917 have sent to review. The rest of the patches are ready too, but they might be affected by changes in bug 1491637 and bug 1436188, so I haven't sent them yet.

2. Bug 1348705 seems to be fixed in another issue. Will try to verify that by a simple test.

So:

High priority issues or issues that having patches:
Bug 1436188 has patches and is waiting for feedback. Bug 1487779 is the follow-up bug for it.
Bug 1491637 has patches and is waiting for review and feedback.

Bug 944918, 1423917, 1493262 should be fixed in bug 1423917. However, since the range of them are a little vague to me, so that I will monitor whether they are fixed by checking the data in Bug 1436188.

Bug 1436128 should be taken care in the local storage next generation.

Others:
Bug 1267349 and 1502077 is related to having a proper error message so their priorities are low to me.
Bug 1395133 is to add a test so that its priority is low to me.
Depends on: 1504535

Updated

5 months ago
Depends on: 1519822
See Also: → 1517531
Depends on: 1322569
Summary: The War on Storage Initialization Failures [meta] → [meta] The War on Storage Initialization Failures
No longer depends on: 944918

Updated

a month ago
See Also: → 1541370

Updated

a month ago
No longer blocks: Session_managers
You need to log in before you can comment on or make changes to this bug.