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

Marvellous Suspender vs Chrome Memory Saver #218

Closed
Crypto-Spartan opened this issue Sep 16, 2023 · 5 comments
Closed

Marvellous Suspender vs Chrome Memory Saver #218

Crypto-Spartan opened this issue Sep 16, 2023 · 5 comments
Assignees

Comments

@Crypto-Spartan
Copy link

Hi, I'm looking for information regarding differences between Marvellous Suspender and Chrome's Memory Saver. A couple of questions I had:

  • what are the pros/cons of using one over the other? is one objectively better? or is it a scenario case where one might save more memory, but the other provides a snappier experience?
  • what problems (if any) exist if you have Chrome Memory Saver enabled while also using Marvellous Suspender?

I tried to do some research on this, but I wasn't able to find many discussions around it. I came across this reddit post, but it seems that no one there knew the answer either: https://reddit.com/r/chrome/comments/11uesf8/chrome_memory_saver_vs_the_marvellous_suspender/

I would be very grateful for any information regarding this, even if it's not a lot

@Technetium1
Copy link

No issues using both at once. Memory saver in Chrome isn't on a 'timer of inactivity', so it unloads when it feels like it. If you do really, really large sessions, then the memory saver is inferior in comparison.

@Crypto-Spartan
Copy link
Author

Crypto-Spartan commented Sep 18, 2023

Can you provide any additional details as to how the two functions work and how they interact with one another? I haven't been able to find a lot of documentation in my searches.

@Technetium1
Copy link

I'm telling just based off of my experiences. You won't find any documentation on this… You'll have to actually read some of the code that does the suspension in Chrome's memory saver to know how theirs works.

I don't like that memory saver when used alone will reload the tab when you go to it. Sometimes I tab through 20 suspended tabs in a window to find a specific thing, and I don't want to reload all 20 pages. That's definitely a big difference, because here a custom suspend page is rendered, which only optionally reloads on focus.

Maybe you want to start at this: https://github.com/gioxx/MarvellousSuspender/blob/master/src/js/gsTabSuspendManager.js

Google is in charge of doing heuristics to determine what to suspend, no such thing here, only a timer.
chromium/chromium@fbb6598
chromium/chromium@dc53268

@eNdEmiOn
Copy link

Yeah I wouldn't mind some more info as well. I mean why for instance am I observing my tabs graying out twice as in two steps of opaqueness? Suspend, hibernate what are the differences?

One important difference I can tell you about though is that chromes memory saver won't help speed up the startup process of your browser as it will not remember which tabs were suspended so it will reload everything.

@Crypto-Spartan
Copy link
Author

Anyone coming to this thread looking for info, check out #197, specifically here & here.

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

4 participants