Closed Bug 1425019 Opened 7 years ago Closed 5 years ago

NoScript fails to sync with "Maximum bytes per object exceeded (16507 > 16384 Bytes)"

Categories

(WebExtensions :: Storage, defect, P3)

57 Branch
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1484968

People

(Reporter: unimportant.stuff, Unassigned)

References

Details

Attachments

(3 files)

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:57.0) Gecko/20100101 Firefox/57.0 Build ID: 20171206182557 Steps to reproduce: I use FF 57.0.2, 32bit on a PC and 64bit on a Laptop. Using Sync works like expected except for the time of last sync. I manually or automatically sync both computers. Actual results: On the PC the time of the last sync is always displayed as "Letzter Sync: 25. November". On the laptop it is the expected date/time Expected results: I expect to also show the time of the last sync on the PC.
These are some settings on my PC before another sync. Filtered by services.sync.*last
These are some settings on my PC after another sync. Filtered by services.sync.*last
Component: Untriaged → Sync
If you visit about:sync-log on the PC with the incorrect lastSync time, I suspect you will find some error logs there - would it be possible for you to attach one of them here?
Flags: needinfo?(unimportant.stuff)
There is indeed an error: 1513198015293 Sync.Engine.Extension-Storage ERROR Syncing {73a6fe31-595d-460b-a920-fcc0f8843232}: request failed: Error: HTTP 507; Error: HTTP 507 Insufficient Storage: Resource access is forbidden for this user (Maximum bytes per object exceeded (16507 > 16384 Bytes.) (resource://services-common/kinto-http-client.js:2354:21) JS Stack trace: formatResponse@kinto-http-client.js:2377:21 < processResponse@kinto-http-client.js:2352:14 1513198015293 Sync.Engine.Extension-Storage WARN Syncing failed: Error: HTTP 507; Error: HTTP 507 Insufficient Storage: Resource access is forbidden for this user (Maximum bytes per object exceeded (16507 > 16384 Bytes.) (resource://services-common/kinto-http-client.js:2354:21) JS Stack trace: formatResponse@kinto-http-client.js:2377:21 < processResponse@kinto-http-client.js:2352:14 See also attached file
Flags: needinfo?(unimportant.stuff)
It seems that NoScript cannot sync. ID=73a6fe31-595d-460b-a920-fcc0f8843232 When I disable syncing of Add-ons the last sync timestamp updates. Enabling syncing of Add-ons again stops updating the timestamp. Disabling only NoScript also helps solving this bug.
When I enable NoScript and remove some of the trusted sites by setting them to "Default", syncing no longer makes any problems. So it depends on the size of data NoScript wants to exchange.
Thanks! I've created bug 1425152 for the fact that Sync doesn't handle this persistent failure case very well and I'll morph this bug into the specific "Maximum bytes per object exceeded" error in that log.
Component: Sync → WebExtensions: Storage
Product: Firefox → Toolkit
Summary: time of last sync not updated → NoScript fails to sync with "Maximum bytes per object exceeded (16507 > 16384 Bytes)"
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P3
Is there any suggested work-around? What's the quota policy, exactly? Is the 16KB limit per-extension, per root key or what? I've got user reporting failures with 130KB and more, I'd like to make their lives easier. Thanks!
Flags: needinfo?(markh)
According to https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/storage/sync, there is a 100k limit. The only work-around I know of is to store less than that.
Flags: needinfo?(markh)
Product: Toolkit → WebExtensions
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: