Question regarding slowdowns in PM (disk useage)

[KlarkKentThe3rd]

Throughout the years I was under the impression that browsers lag due to the browser itself, poorly coded websites, and my hard drive being old and close to full.

However, I checked the disk useage (never did before), and I am seeing this. So many gigabytes. Is this even normal?
(I am using the latest community build)

[Moonraker]

cache build up.?.
Have you cleared the cache or have PM clear on exit.?

[KlarkKentThe3rd]

I have limited the cache to be 350mb only. That, and (pics attached)

[KlarkKentThe3rd]

Whoever moved my thread here, thanks.

[billmcct]

Something's lying to you. No way you could use 132.9% CPU. CPU use can never get past 100%.

[Moonchild]

The main question is: how long is your session? days? weeks? Judging by the CPU time used you haven't restarted the browser in forever, in which case the cumulative read/write numbers are quite normal.

[KlarkKentThe3rd]

Good question. I have restarted the browser at least twice in the past 3 days. Unless quitting and re-opening in 30 minutes is not the same as restarting.

Whenever something causes PM to slow down and my CPU to heat up, it also corresponds with the heavy load disk writing, as I now discovered. And yes, the CPU does go above 100% in these cases. I still have no idea what causes this, since closing YT usually does nothing, even after several minutes. Perhaps someone's mining crypto, sounds crazy but not impossible.

Right now, I have 50% CPU, 700mb being written, and 2.3GB of RAM used. Now it's all fine. And despite 1 30min YT video playing in 720p.

[Andrew Herbert]

It also happens to me (except the slowdowns part) when accessing JS-heavy websites, even after closing them.

[KlarkKentThe3rd]

You don't have slowdowns because you have a stronger CPU/more RAM, I can bet on it.

[KlarkKentThe3rd]

This might be coming from a non-developer, but would it be possible to write an extension that strips the browser from/stops any JS that is not coming from any currently opened window? If you visit a JS heavy site, and it slows down PM for many minutes later, even after you leave, then this might be a potential solution.

Alternatively, just stop all scripts currently running. Like, kill and delete all scripts. Less convoluted to program, could easily help with slowdown.

[Moonchild]

Extensions can do many things but they can't control SpiderMonkey internal runtimes.

[New Tobin Paradigm]

Even if a binary extension could issue commands to xpconnect to instruct the JS Engine that wouldn't stop or really affect DOM's direct usage of the JS API.

[The Squash]

Something's lying to you. No way you could use 132.9% CPU. CPU use can never get past 100%.

It's called multi-core processors. Evidently OS X's process manager does not work in Solaris mode (which divides the CPU usage by the number of CPUs in the system), which makes sense because OS X was based partly on BSD, not at all on Solaris.

[KlarkKentThe3rd]

I never thought I'd see the day Solaris being mentioned here.

[The Squash]

What's that supposed to mean? You mean you didn't expect that Solaris would be mentioned at all on an OS X-specific part of the board?

And, I'll admit, Solaris does not come to mind readily when thinking about this browser.

[KlarkKentThe3rd]

Looks like the magic bullet was realizing I was running too many add-ons that I wasn't actually using, some of them CPU-intensive and possibly conflicting with each other.

Half of those running right now are borderline passive, not doing anything until asked. nMatrix, uBlock, PureURL, arranged from most the least CPU using. This works, and now the excessive slowdowns are gone.

[dbsoft]

Half of those running right now are borderline passive, not doing anything until asked. nMatrix, uBlock, PureURL, arranged from most the least CPU using. This works, and now the excessive slowdowns are gone.

So it was 1 or more of those 3 you disabled?

[moonbat]

Why did you disable Pale Moon Commander?
It is purely a front end for some advanced settings to keep from having to mess manually with about:config, and it doesn't run in the background or interfere with anything else.