You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A recent memory report of my Firefox showed that the extension process is holding to over 200MB of images, basically all unsplash.com, each around 2MB, meaning over 100 images. The only extension that loads them is Tabliss.
I'm not sure why it's necessary to cache them (in memory) on top of the browser cache. Unsplash sends a Cache-Control header with max-age=31536000, or one year. Frequent enough loads (15 min in my case, 1 hour/day/week as longer options) should be enough to prevent them from being evicted, so even a "naive" request would be from local cache.
The text was updated successfully, but these errors were encountered:
A recent memory report of my Firefox showed that the extension process is holding to over 200MB of images, basically all unsplash.com, each around 2MB, meaning over 100 images. The only extension that loads them is Tabliss.
This part came across when examining the source:
tabliss/src/plugins/backgrounds/unsplash/Unsplash.tsx
Lines 34 to 42 in 765a3f0
I'm not sure why it's necessary to cache them (in memory) on top of the browser cache. Unsplash sends a Cache-Control header with
max-age=31536000
, or one year. Frequent enough loads (15 min in my case, 1 hour/day/week as longer options) should be enough to prevent them from being evicted, so even a "naive" request would be from local cache.The text was updated successfully, but these errors were encountered: