search

rNeomy / tab-suspender

Automatically suspend (hibernate) inactive tabs to free up system resources; This project is discontinued in favor of https://add0n.com/tab-discard.html
http://add0n.com/tab-suspender.html
Mozilla Public License 2.0
112 stars 32 forks source link

Stopped working after latest update #61

Open EC-O-DE opened 7 years ago

EC-O-DE commented 7 years ago

Stopped working after latest update

aurelg commented 7 years ago

Same here, the current version (0.2.4) does not work with Firefox Developer Edition 58.0b1 (64-bit) running on Archlinux.

xxxxxxccccccccccc commented 7 years ago

I noticed what you're experiencing around the same time of this thread, so:

The issue is not that the extension doesn't work... it's that the extension seems to STOP working after X time. Tabs cease to auto-suspend, and manually trying to suspend like from the right click menus does nothing at all. Restart the browser, and it works again.

Using Nightly 58.0a1 here, but I first noticed this before 58 so it isn't a 58 issue. 57+? Might be, OP didn't specify his version.

irvinm commented 7 years ago

@rNeomy, I believe this is related to the "native" usage of the new tab discard method.

All, the new native method was only introduced in FF58. If you unselect "use native method" in the options for tab suspender, things should work. (I was seeing the same with FF58b1 and disabling the native method, things worked as they did in previous releases. There might be a problem with the new API in Firefox itself or in the way it was implemented)

EC-O-DE commented 7 years ago

I use this om Opera 49. Latest ver 0.2.5 working again!

gbakeman commented 6 years ago

According this issue at Mozilla, this is implemented in Firefox 58. @irvinm so is the native method working ok for you now?

irvinm commented 6 years ago

I played with FF58b and FF59a a little this morning and everything worked fine with either the "native" option enabled or disabled. However, I am unsure if there is any visual way to tell if the addon is using the native browser implementation of discard or not as the standard discarded page is loaded in both situations.

I didn't try it with my large browser session (500+ tabs), but merely tried a single tab. [Maybe the performance of the native implementation or the resource savings would be easier to see with the larger session]