1646022 - Initialization shouldn't fail when there is no database and padding files

Status: RESOLVED DUPLICATE of bug 1645943

(Core :: Storage: Cache API, defect, P1)

Description

[Tom Tung [:tt, :ttung]]

When we are in
CacheQuotaClient::GetUsageForOriginInternal
Steps here are:

• Get origin directory
• Append cache directory into file path
• Get padding size
  • Get from temporary padding file
  • If fails, get from final padding file
  • If fails, get from cache.sqlite database
  • If fails, stop and break the storage init
    ...

Here, however, it's possible that there is no cache.sqlite database, and any padding files.
We shouldn't block the initialization due to this.

Comment 1

[Tom Tung [:tt, :ttung]]

Note that when we are in this situation, it's probably because we crashed in the previous session

Comment 2

[Tom Tung [:tt, :ttung]]

(In reply to Tom Tung [:tt, :ttung] from comment #0)

Here, however, it's possible that there is no cache.sqlite database, and any padding files.
We shouldn't block the initialization due to this.

I might miss some other factors for causing the issue.

I wrote a test to verify this by creating an empty cache folder, but the test succeeded.
https://treeherder.mozilla.org/#/jobs?repo=try&revision=61370715eefe4962beea711a110c0366e8799214