On 12/12/24 04:50, Paul M. Foster wrote:
On 12/11/24 15:08, Van Snyder wrote:
After Firefox has been running for a few days my Debian 12.5 gets
really slow. The mouse jerks when it works at all. It takes a minute
or two for wndows to close or top. At the moment, Firefox has 19
processes running. Memory is half full, and swap is about 10% used.
When I kill Firefox and restart, things go back to normal for a few
hours.
What alternatives that aren't such pigs do you recommend?
I call this "memory leakage". I don't know if actual code bugs, or the
sloppy way Firefox allocates and frees memory. As far as I know, all
browsers suffer from this. If you find one which doesn't, let us know.
Paul
Many years ago, I believe when I was being taught 'C' programming, we
were taught to use two instructions named malloc and (I believe the
other important corresponding instruction), dealloc, and, some software,
including some web browsers (and, the vile javascript) seem to disregard
that instruction and its importance, which is kind of like running an
internal combustion engine without a governor, or, parking a vehicle on
a slope, without engaging the handbrake.
Memory leakage, by its wording, appears to indicate that the memory gets
freed, by leakage (like diarrhoea or incontinence), whereas, what seems
to be occurring, is more like constipation, where the contents are not
being freed, cumulatively increasing the pressure, causing the computer
to not feel well, and "fall over".
..
Bret Busby
Armadale
West Australia
(UTC+0800)
..............
