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

show screenshots of hibernated pages #8

Open
343max opened this issue Mar 15, 2013 · 5 comments
Open

show screenshots of hibernated pages #8

343max opened this issue Mar 15, 2013 · 5 comments
Labels

Comments

@343max
Copy link
Owner

343max commented Mar 15, 2013

No description provided.

@HorayNarea
Copy link
Collaborator

i tried to implement this via chrome.tabs.captureVisibleTab but that only takes a screenshot of (surpise surprise!) the visible(==focused==active) tab
one could make a screenshot-loop that sets every tab as active, takes a screenshot and sets the tab as inactive again but this means a lot of tab switching and "flickering" and probably will slow down massively with many tabs

i also looked into (weird) alternative methods like chrome.tabCapture but it either didn't work at all or was unreliable and slow as hell

in short: at the current state of Chrome-APIs i think this feature is impossible (or at least very hard) while still having a nice user-experience

@HorayNarea
Copy link
Collaborator

untested idea: we might inject JS into every page that makes a screenshot via captureVisibleTab() when the tab gets focus and use it when hibernating this tab
(but this could make the extension a bit memory-heavy which would make it kind of pointless)

@343max
Copy link
Owner Author

343max commented Feb 19, 2016

I tried it a few times but it seems to be impossible for security reasons.

@elgalu
Copy link

elgalu commented Sep 7, 2016

I found 2 extensions that are able to do this, perhaps you can try to investigate how:

  • Tab Suspender was quite slow for my taste.
  • Tab Hibernate seems to be working faster, note screen shots are optional via checkbox.

Even though there seems to be not much saving in memory what is also interesting is to avoid having all those background JS scripts running on the tabs which peaks the CPU ;)

@HorayNarea
Copy link
Collaborator

Thanks for the input, I will look into those extensions!
And I agree, a minimum CPU usage (optimally zero) should be a priority

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

No branches or pull requests

3 participants