search

samueljun / tomato-clock

Tomato Clock is a simple browser extension for managing your productivity.
GNU General Public License v3.0
331 stars 55 forks source link

Firefox freezes intermittently unless the extension is disabled/removed #71

Closed dharmit closed 4 years ago

dharmit commented 5 years ago

Describe the bug

I'm not sure that this extension is the reason for the freeze I'm observing on Firefox but I don't see a way of being sure about it other than opening an issue. So, kindly do not take this as if I'm blaming the extension. On the contrary I love the extension and it has given me insights on my working pattern and made me think how I can work better.

When I start a pomodoro cycle, Firefox freezes randomly after some time and becomes completely unresponsive to mouse or keyboard inputs. This goes on for quite a few seconds and then Firefox becomes usable once again without changing anything on the system. I have started facing this issue since about a week.

To Reproduce

  1. Start a pomodoro cycle and wait for some time

Expected behavior Firefox should not freeze

Screenshots N/A

Desktop (please complete the following information):

Additional context

dharmit commented 5 years ago

A recent observation: pomodoro cycle doesn't need to be in progress for the issue to happen.

When I started facing this issue, I tried to isolate its cause by disabling all extensions and enabling them again one after the other till the issue surfaces.

samueljun commented 4 years ago

Closing since it sounds like it's something else, feel free to reopen if it's something with the extension.

whym commented 4 years ago

I experienced similar freezes constantly. It might have to do with Firefox Sync with a somewhat large timeline data (I think tens of kilo bytes) on Tomato Clock - my current workaround is to disable syncing addons. See below for more.

@dharmit: Do you have Firefox Sync enabled? If your Firefox recovers after a freeze, could you try openning about:sync-log and check the content of the newest file? You might see a line containing "ERROR Syncing jid1-Kt2kYYgi32zPuw@jetpack" there. If so, I thik we are experiencing the same thing.

Here is some of the errors I got:

1573087092551   Sync.Engine.Extension-Storage   ERROR   Syncing jid1-Kt2kYYgi32zPuw@jetpack: request failed: Error: HTTP 507 Insufficient Storage: Resource access is forbidden for this user (Maximum bytes per object exceeded " "(65275 > 16384 Bytes.)(resource://services-common/kinto-http-client.js:2771:5) JS Stack trace: ServerResponse@kinto-http-client.js:2771:5
processResponse@kinto-http-client.js:2925:13

1573020187874   Sync.Engine.Extension-Storage   ERROR   Syncing jid1-Kt2kYYgi32zPuw@jetpack: request failed: Error: Timeout while trying to access https://webextensions.settings.services.mozilla.com/v1/batch with {"method":"POST","headers":{"Accept":"application/json","Content-Type":"application/json","Authorization":"**** (suppressed)"},"body":"{\"defaults\":{\"headers\":{\"Authorization\":\"Bearer 688dec51a1e8309ba5a3d620a2a47260197a9081f3025020776ecb10f0ec5aa3\"}},\"requests\":[{\"method\":\"PUT\",\"path\":\"/buckets/default/collections/ext-5jGil0jc6a52idyb0ROW9UR0KWtnS6LW_fmP-VAMTMo/records/id-zm-k9x-E_uT_mU4xXhVNu_r7qCV9VqOlFvk1dYLWs38\",\"headers\":{\"If-Match\":\"\\\"1523430040159\\\"\"},\"body\":{\"data\":{\"ciphertext\":

(I cut the above line after "ciphertext" - the rest seemed just ... tens of kilo bytes of encrypted data.)

I tried disabling Firefox Sync for addons, and the problem disappeared as far as I can see. (which is my current workaround, as I personally don't need addon settings to be synced at the moment.) No error was shown in about:sync-log after that.

Since one of the errors says "Insufficient Storage", could it be the case that the timeline data is too large to be synced? My Tomato Clock export is somewhere around 42 kilo bytes, which is apparently larger than the quota written in https://bugzilla.mozilla.org/show_bug.cgi?id=1413949#c5 . I don't know how it could result in hanging up the browser, though.

dharmit commented 4 years ago

@dharmit: Do you have Firefox Sync enabled? If your Firefox recovers after a freeze, could you try openning about:sync-log and check the content of the newest file?

I'm not facing the freeze issue anymore. But I do see an error similar to yours in the about:sync-log. However, it doesn't freeze the browser anymore.