Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Caches don't have limits/expirations
See original GitHub issueWe’re using the storage to cache the release count and the users’ full name. These caches don’t expire and they just pile up. There should be a mechanism to either regularly purge the cache or to make them expire.
A thought was to use good ol’ cookies in the background.js (yes they work in there) since the expiration is handled natively and new items push out the old items once the limit is reached — just like you’d expect from a cache.
However cookies are limited to 4KB (instead of 5MB), which maybe fits around 100 user names and 40 release counts.
Ideas?
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I would just go the easy route and purge the cache every x days (100?).
Make it every 30 days and I’m 👍