Thorium

[Guest]

12 hours ago, Dave-H said:

My copy of Thorium has now started running out of memory when scrolling on sites like Facebook and Instagram.
It didn't use to do this, it was much better than Supermium in that respect, and it's been fine for months.
Anyone any idea why it would suddenly start doing this, I haven't knowingly changed anything which might have caused it?
Of course, the sites themselves may have changed, but any changes made haven't caused any obvious visual changes in them.

You could try using the “Click to load” feature of uBlock Origin to reduce the resources consumed by the browser in heavy web sites:

https://x.com/gorhill/status/1377613404794421258

Try to see if this list of filters from Yokoffing solves (at least part of) your problem.
If any rules are not to your liking, you can disable them by entering !
You can also copy only the rules you are interested in into "My filters":

https://github.com/yokoffing/filterlists/blob/main/click2load.txt

Quote

Turns many third-party audio and video players into click-to-load placeholders which only load once a user clicks on it. This list speeds up page load, uses less bandwidth and browser resources, and reduces privacy exposure (by contacting fewer domains during page load). The player will load by clicking on the placeholder.

 

[Dave-H]

@Dixel

Thanks, I've added the '--enable-low-end-device' switch.
I'll report back as to whether it helps or not.

@Sampei.Nihira

Thanks, but I've stopped using uBlock Origin, and I'm now using uBlock Origin Lite.
uBlock Origin is going to be blocked on Chromium browsers soon, isn't it?

[NotHereToPlayGames]

10 minutes ago, Dave-H said:

Thanks, I've added the '--enable-low-end-device' switch.
I'll report back as to whether it helps or not.

I did give it a trial run in Thorium earlier today.

I was going to post screencaps but was afraid that I would appear "biased".  I'm honestly not, lol.

My test-case was WinXP x86 dual-core with only 1 GB RAM.
My Thorium with one tab (Speedomter 2.1) with this enabled used approx 360 MB of RAM.
Without this switch, the same one tab (Speedometer 2.1) used approx 480 MB of RAM.

The switch improved my Speedometer 2.1 score - but only by 6 points which I would consider within "margin of error".

On an old-but-not-ancient hardware running Win10 with eight cores and 16 MB RAM, I forget the RAM consumption but my Speedometer score DECREASED from 134 all the way down to 87 !!!
I ran the tests four times both with and without this switch, all four tests in each case was within 3 or 4 points of each other.  Win10, eight cores, and 16 MB RAM definitely does NOT like this switch.

[NotHereToPlayGames]

Here at work (Win10 x64, 32 GB RAM, 12th Gen i7), my score decreases from 170 all the way down to 138.

I am aware that Win10 is not our reference point here (Thorium is not needed on Win10), my only point here is that the switch in question should be "vetted" and not just by "gut feelings".  

[Guest]

41 minutes ago, Dave-H said:

@Dixel

Thanks, I've added the '--enable-low-end-device' switch.
I'll report back as to whether it helps or not.

@Sampei.Nihira

Thanks, but I've stopped using uBlock Origin, and I'm now using uBlock Origin Lite.
uBlock Origin is going to be blocked on Chromium browsers soon, isn't it?

Without the right policy set by users or developers,yes.

But with uBlock Origin Lite, if you have memory problems, it should be better because the content blocking is done by the browser itself.
I can only advise you with FB and Instagram to reduce the slider to “Basic” which consumes less RAM.

[Dave-H]

No difference with the switch added on my XP system.
Still eating RAM, and then the tab process crashes.

[Dave-H]

2 minutes ago, Sampei.Nihira said:

Without the right policy set by users or developers,yes.

But with uBlock Origin Lite, if you have memory problems, it should be better because the content blocking is done by the browser itself.
I can only advise you with FB and Instagram to reduce the slider to “Basic” which consumes less RAM.

Thank you, that's probably the problem!

I had to turn uBlock Origin Lite up to maximum filtering on Facebook and Instagram as otherwise the endless annoying 'sponsored posts' still get through.
Looks like I'll just have to live with it as it is.

[Guest]

33 minutes ago, Dave-H said:

Thank you, that's probably the problem!

I had to turn uBlock Origin Lite up to maximum filtering on Facebook and Instagram as otherwise the endless annoying 'sponsored posts' still get through.
Looks like I'll just have to live with it as it is.

If you lower the slider to basic ONLY in FB and Instagram the other websites will continue to have the slider at the value you set in the general rules.

P.S.

It would be better to set optimal and then raise to maximum only where it is necessary (for example, on MSFN).

P.S.1

Also try disabling any other extensions (which consume RAM) when you visit those problematic websites.
Maybe you can increase the slider to maximum without more problems.
 

Edited September 2, 2024 by Sampei.Nihira

[AstroSkipper]

Facebook as well as all these social media sites have become overbloated more and more day by day and year by year. I've just logged in an old FB account in Mypal 68, and the RAM eating started. Only my FB front page open, and Mypal 68 consumes 750 MB. I won't test this crappy service in Thorium as there is not enough RAM for such bad sites. I think such social media sites are more made for mobile devices the last years. On Android, there are corresponding apps for each of these services. Personally, I do not use these services. And I hate them all.

[NotHereToPlayGames]

27 minutes ago, AstroSkipper said:

And I hate them all.

  Agreed!  Same here.  I don't even HAVE an old FB (or Instagram, or Twitter, or TikTok, et cetera) account.  So you are "closer" than I am, lol.

[UCyborg]

Scrolling too far? FB isn't that bad, all things considered. I can imagine the tab's process running out of memory if running 32-bit browser. I mean, all that content must be stored somewhere. Does memory at least get released when navigating away?

7 hours ago, AstroSkipper said:

Only my FB front page open, and Mypal 68 consumes 750 MB.

LOL, consumption on my FB front page is about 205 MB with Firefox 110 here, without scrolling down of course.

I got to 2 GB scrolling one random page, then I stopped, should replace 32-bit Firefox with 64-bit at some point. Not that I really need to go that far on any such heavy page, but since I got the hardware...

Well, honestly, consumption could be heavily reduced by employing pagination, but why do that when everyone has gigabytes of RAM and can keep people hooked without having to click to navigate to new page.

Edited September 2, 2024 by UCyborg

[VistaLover]

On 9/1/2024 at 8:29 PM, Dave-H said:

Anyone any idea why it would suddenly start doing this, I haven't knowingly changed anything which might have caused it?

8 hours ago, Dave-H said:

I had to turn uBlock Origin Lite up to maximum filtering on Facebook and Instagram as otherwise the endless annoying 'sponsored posts' still get through.

... Oops dear Dave  , isn't that a contradiction of sorts?  

9 hours ago, Dave-H said:

uBlock Origin is going to be blocked on Chromium browsers soon, isn't it?

... On Google's  Chrome sure, but the Supermium (on which Thorium-Legacy is based on) and Thorium authors have different plans : 

https://www.win32subsystem.live/supermium/

Quote

Unlike Google Chrome, Manifest V2 is NOT slated for removal from the Supermium browser.
You may download the latest builds of uBO directly from the project's GitHub, in the event that it is not obtainable from the Chrome Web Store.
The latest, feature-complete version of uBO will be made available here if/when Manifest V2 builds for Chromium are discontinued.

https://github.com/Alex313031/thorium/discussions/797#discussioncomment-10508470

Quote

I will be restoring the MV2 code after it is removed. However, MV2 extensions will have to be installed manually.

... provided, of course, gorhill (or someone else) keeps developing the MV2 uBO implementation...

Edited September 2, 2024 by VistaLover

[UCyborg]

Oops, I missed a little detail, you might want to have spare CPU cores for Facebook. Because one keeps being hammered at the very least. On Supermium on XP, even two can be hammered while viewing single tab. And I thought this s*** only happens on UXP browsers. So my not so bad evaluation for FB came from my PC still being usable and not paying attention to CPU, but taking this into account...

This is why you need gaming PC for web these days. Because that behavior is normal for games. 

[Dixel]

I share everyone's frustration towards the "modern" web, though in this case the problem lies within the browser, even simple text directories have a huge leak.

https://github.com/win32ss/supermium/issues/841

[Dixel]

"I can confirm this as well. Renderer process commits about 2.5 GB on Supermium 126 x64 when it finishes loading that page, well above any practical 32 bit limit. Google Chrome 126 is even worse at about 2.75 GB. But then I tried Google Chrome 49, and about 300 MB is committed and the page loads successfully."

https://github.com/win32ss/supermium/issues/841#issuecomment-2322122240