Not working anymore (last 3 months)

[circuitikzuser]

I nw suddenly get tabs not shutting down after the amount of minutes configured. It used to work great for years, until a few months ago when trouble started.

[autonome]

Thanks for reporting, I'll test asap.

On Wed, Aug 21, 2024, at 05:44, circuitikzuser wrote:

I nw suddenly get tabs not shutting down after the amount of minutes configured. It used to work great for years, until a few months ago when trouble started.

— Reply to this email directly, view it on GitHub https://github.com/autonome/Dormancy/issues/46, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAMHNZMVZXMYHRG7GDAMQDZSQEJDAVCNFSM6AAAAABM3EGFT2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ3TMOJXHEYDCNA. You are receiving this because you are subscribed to this thread.Message ID: @.***>

[autonome]

i just tested and it worked fine on latest Firefox.

can you share more about your system and what settings you are testing?

[circuitikzuser]

Thank you for the response. It is appreciated. I understand that it will work for you, but there are a lot of things users can find to make it not work properly. System: NAME="MX" VERSION="23.3 (Libretto)" ID="mx" VERSION_ID="23.3" PRETTY_NAME="MX 23.3 (Libretto)" ANSI_COLOR="0;34" HOME_URL="https://mxlinux.org" BUG_REPORT_URL="https://mxlinux.org" BASE=MX PRETTY_NAME="MX 23.3 Libretto" DISTRIB_ID=MX DISTRIB_RELEASE=23.3 DISTRIB_CODENAME="Libretto" DISTRIB_DESCRIPTION="MX 23.3 Libretto" PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=debian

Browser Firefox (various versions on different pcs. Result the same on all)

The setting I am using is 10min timeout for all tabs, without active tab "keep-alive" I found that since I am using pinned tabs, dormancy works unreliably. Dormancy is supposed to hibernate all tabs, but if I leave my browser for a while with say 10 pinned tabs open, then after a while I get 100% cpu "Isolated Web Co.." (a tab process) processes running that I first have to close to get my browser operable again. This happened the entire last year on different versions of Firefox. This never happened before I started pinning tabs.

[autonome]

The setting I am using is 10min timeout for all tabs, without active tab "keep-alive"

Ok, thanks this the default settings.

I found that since I am using pinned tabs, dormancy works unreliably. Dormancy is supposed to hibernate all tabs, but if I leave my browser for a while with say 10 pinned tabs open

Ok, I'll test with pinned tabs.

after a while I get 100% cpu "Isolated Web Co.." (a tab process) processes running that I first have to close to get my browser operable again. This happened the entire last year on different versions of Firefox. This never happened before I started pinning tabs.

Can you test without having that specific URL loaded? Or can you share that URL for me to test? I'll test the scenario above, but this sounds like it's problem where the extension doesn't function because a page you have loaded is breaking Firefox.

[circuitikzuser]

I will have to wait until the entire thing borks again. If tabs are pinned however, it is almost impossible to find which tab was killed when I kill the high cpu process for that tab. I will have to figure out a way to identify a Tab by PID and I currently dont know how to do that. It starts happening after pinned tabs are active for more than about 6 hours. Websites are so infested with the default google and what-not embeds that comes with the web-development software. Most of the embeds are not friendly at all and intentionally malicious in my opinion. It will take some time to figure out how to catch the pinned tabs, so dont waste too much time on it until I can get a collection of sites that does this. Unpinned, this would have been easy.

To me Dormancy is very valuable to stop malicious processes which starts running when you are not using a browser for a few hours. That behavior is clearly malicious and would be nice if Dormancy could stop it too.

[circuitikzuser]

I managed to get an addon to manipulate the tab behavior such that I will see which sites are the culprits during pinned tabs. I will let you know once it happens again, but it might be a while before I respond.

[circuitikzuser]

Question: How difficult is for you to just grayscale a tab description, the block with the name at the top (not content) when the tab goes into hibernation ? Then when accessed and loading it goes back to color. That will help a heck of a lot and also make dormancy obvious that it is working. Would be really helpful, as it would have debugged this issue fast. Just a suggestion.

[autonome]

a visual indicator of some kind is a great idea. can you file a separate issue for that?

On Sat, Aug 24, 2024, at 12:31, circuitikzuser wrote:

Question: How difficult is for you to just grayscale a tab description, the block with the name at the top (not content) when the tab goes into hibernation ? Then when accessed and loading it goes back to color. That will help a heck of a lot and also make dormancy obvious that it is working. Would be really helpful, as it would have debugged this issue fast. Just a suggestion.

— Reply to this email directly, view it on GitHub https://github.com/autonome/Dormancy/issues/46#issuecomment-2308330589, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAMHN7O6H46EZ55FJC6BQLZTBOGVAVCNFSM6AAAAABM3EGFT2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBYGMZTANJYHE. You are receiving this because you commented.Message ID: @.***>

[circuitikzuser]

I will try to file a separate issue. I had my browser freeze up again yesterday due to a tab that was running away with +100cpu bypassing dormancy. As soon as I killed it in top, browser worked fine again. Unfortunately no way to see which tab is it as it is pinned and happens only if pinned. Indicator should help to see what was successfully made dormant and what not,

[circuitikzuser]

I found one sure culprit that circumvent dormancy. Note: There are more..

imgur.com

The thing seemingly goes wild spontaneously after a day or so after being dormant. Sometimes it takes days, but it does go wild eventually. Once I kill that tab in cron my browser can be used again.

The only way you can really make a tab dormant is to change the url with a random number say google.com to google.com1 when going into dormancy, making it unroutable, then when a user click on a tab then it reverts back to the previous url e.g. from google.com1 back to google.com. There are too many malicious code in pages these days with the ready made web-development platforms that have all the google and facebook and what not other spooks' crap already built in. Changing the URL will take care of this long delay maliciousness seemingly circumventing dormancy. I am constantly looking for more, but they are difficult to catch as I kill them by process and have to kill a couple before I stumble on the real culprit. So it take a lot of trials to identify the real one. If dormany indicated on the tab that it is dormant, this will be caught way easier.

[autonome]

All the extension is doing is calling an API which tells the browser to put a tab to sleep.

If the tab wakes up for some other reason, there's nothing Dormancy can do about that.

The extension ignores pinned tabs, so not putting those to sleep is expected.

However, something that is actually possible is that the code handling those tab ids has a bug of some kind. In that case, you might see pinned tabs put to sleep and non-pinned tabs stay awake when they would otherwise be suspended.

I'd like to add visual indicator, but I don't have time right now. Perhaps on an upcoming plane trip...