Coming from #87844.
Summary
Let's investigate the following Onyx storage error: QuotaExceededError: The current transaction exceeded its quota limitations., which accounts for 865,703 (25.7%) of the 3,364,645 analysed errors during a time span of 1 month. Full details about the investigation and methodology are in #87844.
| Platforms |
Top Methods |
| Desktop Firefox (865K — 100%) |
setWithRetry (865K) |
| Retries Exhausted |
Evictions |
No Eviction |
Quota Checks |
>= 95% Full |
Mean % Full |
Quota Check Failed |
| 6,089 |
859,566 |
0 |
859,276 |
0 |
0.0% |
0 |
- 859,276 quota checks with mean 0.0% full — Firefox reports quota exceeded even when overall usage is negligible. The exact quota model (per-transaction, per-write, or other) is unclear from the data alone
- Firefox-exclusive error — different quota behavior from Chromium and Safari
- Eviction is triggered frequently, and relatively few requests end up exhausting retries (6,089), suggesting eviction generally helps resolve this error
Action Items
- Investigate with Sentry, VictoriaLogs and Fullstory to understand user scenarios where this happens — what kind of data is being written when Firefox rejects the transaction?
- Investigate what Firefox's exact quota/transaction limit is and whether we are writing values that are too large for it
Coming from #87844.
Summary
Let's investigate the following Onyx storage error:
QuotaExceededError: The current transaction exceeded its quota limitations., which accounts for 865,703 (25.7%) of the 3,364,645 analysed errors during a time span of 1 month. Full details about the investigation and methodology are in #87844.setWithRetry(865K)Action Items