Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > alt.comp.software.firefox > #12836

Re: Crash with 136.0.2

From Newyana2 <newyana@invalid.nospam>
Newsgroups alt.comp.software.firefox
Subject Re: Crash with 136.0.2
Date 2025-03-22 08:10 -0400
Organization A noiseless patient Spider
Message-ID <vrm9an$3tue4$1@dont-email.me> (permalink)
References <vrltql$3ism3$1@dont-email.me>

Show all headers | View raw


On 3/22/2025 4:53 AM, Jeff Layman wrote:
> Fx 136.0.2 (Linux Mint 22.1) just crashed and would not restart until I 
> rebooted
> 
> I was looking at some Wikipedia pages when it crashed, so nothing 
> unusual. The crash report interface suddenly appeared stating that Fx 
> had encountered a problem and asked if I would like to send a crash 
> report (it's not enabled automatically in the Settings) and did I want 
> to close or restart Fx. I clicked on yes to restart and send the report, 
> and another crash report interface appeared! A third appeared on 
> clicking "yes" in that one. Fx itself did not restart.
> 
> I closed all the boxes and Fx itself. On trying to reopen Fx only a 
> crash report box appeared - not Fx itself. Fx would not open on a second 
> attempt, so I rebooted. It opened ok after reboot without crash report 
> box appearing.
> 
> I thought that 136.0.2 was released to solve problems with 136.0.1!
> 

    I wonder how similar FF is in Linux vs Windows. I don't
remember it actually crashing in many years. Maybe decades.
There was one problem many years ago where FF windows
would multiply out of control. That's the last problem I recall.
Though I'm also using NoScript and a HOSTS file, so probably
not putting much pressure on FF.

    The one big problem I see
is that FF simply can't handle complex interactive pages of a
certain type. For example, my doctor and dentist subcontract
out to companies where the page is fine in Chromium but halfway
there in FF, with lots of curly braces. My webhost control panel
is similar. I now have to keep Chromium on hand for those sites,
and it seems to be getting worse.

   With FF market share down to low single digits, I'm guessing
that commercial webmasters are not testing in FF at all, and
that the scripting engines between the browsers are diverging.

Back to alt.comp.software.firefox | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Crash with 136.0.2 Jeff Layman <Jeff@invalid.invalid> - 2025-03-22 08:53 +0000
  Re: Crash with 136.0.2 Christian Riechers <chriechers@netscape.net.invalid> - 2025-03-22 11:24 +0100
  Re: Crash with 136.0.2 Newyana2 <newyana@invalid.nospam> - 2025-03-22 08:10 -0400
  Re: Crash with 136.0.2 VanguardLH <V@nguard.LH> - 2025-03-22 11:17 -0500
    Re: Crash with 136.0.2 Jeff Layman <Jeff@invalid.invalid> - 2025-03-22 21:55 +0000
      Re: Crash with 136.0.2 VanguardLH <V@nguard.LH> - 2025-03-22 21:54 -0500
        Re: Crash with 136.0.2 Jeff Layman <Jeff@invalid.invalid> - 2025-03-23 13:31 +0000

csiph-web