Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reconsider necessity of putting tab activity state in sessionstore. #36

Open
sfleiter opened this issue Jan 2, 2019 · 0 comments
Open

Comments

@sfleiter
Copy link

sfleiter commented Jan 2, 2019

I asked myself why the tab activity is persisted in sessionstore.
The only reason that came to my mind is extension updates.
If there is no other reason the size of the sessionstore and generated write load be reduced by collecting the data in memory.

For extension updates the data could be persisted in runtime.onUpdateAvailable and loaded in init.

I have some code for that already if desired.
Relates to issue #35.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant