1575322 - Error: HTTP 507 Insufficient Storage: Resource access is forbidden for this user

Status: RESOLVED DUPLICATE of bug 1484968

(WebExtensions :: Storage, defect)

Description

[vtol]

• W10 Pro x_64 1908 b18362.295
• FX 70.0a1 (2019-08-20) (64-bit) (e7e658ec1e98c3868b98195c2ee4b9fe3842172e)

---

1565464470199 Sync.Status DEBUG Status for engine extension-storage: error.engine.reason.unknown_fail
1565464470199 Sync.Status DEBUG Status.service: success.status_ok => error.sync.failed_partial
1565464470199 Sync.ErrorHandler DEBUG extension-storage failed: Error: HTTP 507 Insufficient Storage: Resource access is forbidden for this user (Maximum bytes per object exceeded " "(119079 > 16384 Bytes.)(resource://services-common/kinto-http-client.js:2771:5) JS Stack trace: [e-mail]:2771:5

---

Error does not show in sync logs with FF 68 || 69

Comment 1

[Alex Cornestean]

Hello,

Could you please provide some steps to reproduce this issue along with any other means used while you encountered this bug (used extensions, accessed websites, etc.)? As I do not fully understand how to replicate the results you obtained.

Thanks !

Comment 2

[vtol]

• Exec Synchronise now
• open about:sync-log
• pick and open latest File: error-sync-*.txt
• aforementioned errors showing

Now also reproduced with beta build 66a12ddcf77c6a1548989ced39edf39af78deb80

I would share the full sync-log but not whether it might contain some sensitive data/identifiers that might better not be exposed publicly?

Comment 3

[Jim Mathies [:jimm]]

likely dupe

Comment 4

[Luca Greco [:rpl] [:luca] [:lgreco]]

It looks like an installed extension is using storage.sync and it exceeded the exceeds the QUOTA_BYTES_PER_ITEM limit (See https://bugzilla.mozilla.org/show_bug.cgi?id=1484968#c1, which was the same issue triggered by the side-view testpilot extension).

As I mentioned in Bug 1484968, the QUOTA_BYTES_PER_ITEM limit seems something that we may actually check on the client side (before actually syncing the data with the remote sync storage service), so that a rejected promise could be returned to the caller extension code (to make the extension aware of the sync issue and allow the extension to handle it).

I'm marking this as a dupe of Bug 1484968, and I'll reopen Bug 1484968 and make it depending on Bug 1311516 (implement storage.sync client-side quotas) instead of being marked as a dupe of it.

Comment 5

[vtol]

I am trying to understand what is happening:

• there some limit imposed - where - on the Moz remote sync backend?
• the limit is pertaining number of writes per hour and/or storage size?
• some WX is exceeding that limit - how to figure out which WX it is (I would like to inform the WX developer)?

Comment 6

[Luca Greco [:rpl] [:luca] [:lgreco]]

(In reply to vtol from comment #5)

I am trying to understand what is happening:

• there some limit imposed - where - on the Moz remote sync backend?

It is currently only enforced by the remote sync backend, and so the error is being raised when the extension storage.sync data is being synced back to the server and not when the extension has initially set the value exceeding that quota limit.

• the limit is pertaining number of writes per hour and/or storage size?

The "Maximum bytes per object exceeded" should be the error related to the byte-per-object limit (as also described in the following two bugzilla comments: https://bugzilla.mozilla.org/show_bug.cgi?id=1484968#c1 and https://bugzilla.mozilla.org/show_bug.cgi?id=1413949#c5)

• some WX is exceeding that limit - how to figure out which WX it is (I would like to inform the WX developer)?

The id of the extension that is triggering the sync error should be actually visible in the error-sync-*.txt log files (e.g. as it was for side-view in the error sync logs mentioned in https://bugzilla.mozilla.org/show_bug.cgi?id=1484968#c0).

isn't the extension id logged in the sync errors collected in your Firefox profile?

Comment 7

[vtol]

Thanks you for the extended explanation.

Looking through the log it seems to be

Sync.Engine.Extension-Storage ERROR Syncing [e-mail]: request failed: Error: HTTP 507 Insufficient Storage: Resource access is forbidden for this user (Maximum bytes per object exceeded " "(123111 > 16384 Bytes.)(resource://services-common/kinto-http-client.js:2771:5) JS Stack trace: [e-mail]:2771:5

Comment 8

[vtol]

As x-ref the issue tracker with the WX development https://github.com/brief-rss/brief/issues/379