On 2024-07-19 10:42, The Wanderer wrote:
On 2024-07-19 at 10:34, Gary Dale wrote:
On 2024-07-18 09:52, Gary Dale wrote:
Thanks for the tips guys, but I'm not going to switch to XFCE, I'm
using an old AMD graphics card, it's a desktop machine, and the
problem isn't specific to PDFs - although that seems to be one of
the major triggers.
My system has been upgrading from earlier versions of Debian since
Potato. I've been on Trixie since it became the new testing. This
crashing of Firefox is a new issue - had few problems with Trixie
before that.
I'm beginning to suspect it may be related to my recent
introduction of a Pi-Hole into my network. Could it be a problem
for Firefox when it gets a 0.0.0.0 address returned on a DNS
lookup?
Well, I can confirm it's not the Pi-Hole. Took it out of the DNS
chain and Firefox is still crashing frequently. In fact, it's worse
today. Now it crashes when I'm on Facebook and scrolling down using
the mouse wheel.
What kind of crashes are we talking about? I think there may be an
'about:crashes' or similar type of page built in to Firefox, which could
give information about what it's seen happen.
If it's memory-access-related, there might be benefit to trying to e.g.
run under valgrind, intentionally reproduce a crash, and see what that
tool reports. Then again, Firefox is a sufficiently complex app that
that might not be fruitful.
Have you tried running any hardware-error checking tools, e.g. one of
the memtest suites? Crashes that frequent (with software, versions, and
data which other people do not reproduce the problem with) suggest a
possible hardware issue to my mind, although if nothing else is
exhibiting visible issues that makes the hardware a less likely culprit.
Is there any possibility that something in the library/etc. stack which
Firefox sits on top of may be unreliable, or at least be of different
versions from those which the people not observing the problem are
using? One obvious candidate would probably be the graphics stack
(driver, firmware, etc.), but that's not necessarily the only possibility.
Looking at the submitted and unsubmitted reports, it seems the crashing
started on July 10. It always seems to be "CanvasRenderer" as the
culprit with libxul.so as the guilty module. Firefox was reportedly
installed 32 days ago.
Anyway, the Firefox developers have received dozens of automated crash
reports from me over the past10 days.
I do have a rather old graphics card, but it's an AMD one so the drivers
should be OK. I doubt it's anything else hardware related as I'm not
having problems with other programs.
The only other things of note:
1) my screen does briefly go blank sometimes while doing something
involving windows.
2) Plasma 5 isn't saving my desktop when I reboot.
