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

Really "kill" process to reduce more ram #7

Open
alexalouit opened this issue Feb 8, 2012 · 3 comments
Open

Really "kill" process to reduce more ram #7

alexalouit opened this issue Feb 8, 2012 · 3 comments

Comments

@alexalouit
Copy link

Are there plans to "kill" really the page in question (like the chrome task manager). This increase network traffic when reloading, but would reduce the maximum memory consumption.

@glukki
Copy link
Owner

glukki commented Mar 12, 2012

Explain, how do you imagine the process of unloading killed tabs, please?

Nowadays there is only one way to finally kill tab — close it. Then it is stored up to 10 closed tabs sessions (history, page position, filled forms) by the browser. But there is no possibility to save this session with extension.

@glukki
Copy link
Owner

glukki commented Mar 12, 2012

It's really possible to store current tab url, but history of tab wil be lost.
I could do that as an additionl option :)

@mainiak
Copy link

mainiak commented Aug 19, 2014

Maybe HTML5 History API might help if you insist of keeping it.

@github-staff github-staff deleted a comment Apr 26, 2024
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

3 participants