Firefox ESR 140.2 crashhelper hanging process

271 views
Skip to first unread message

Ruben Gomez

unread,
Aug 21, 2025, 10:11:52 AMAug 21
to enter...@mozilla.org
Upon launching 2 version of firefox for workstations, the 2nd web page is getting stuck and something new not seen on FF 128 version

ps aux|grep firefox
ws141     2312  1.5  2.4 3500020 393748 ?      Sl   08:51   0:15 /opt/firefox/firefox
ws141     2323  0.0  0.0  34944  5244 ?        Sl   08:51   0:00 /opt/firefox-140.2.0esr/crashhelper 2312 9 /tmp/ 10 12

Does crashhelper have to launch every time now with Firefox? 

Can this be disabled? as we are getting a blank page.
  

Ruben Gomez

unread,
Aug 21, 2025, 10:57:50 AMAug 21
to enter...@mozilla.org, Ruben Gomez
oh nvm I just tried https://stackoverflow.com/questions/28393544/disable-crash-reports-of-firefox-in-linux

export MOZ_CRASHREPORTER_DISABLE=1

that worked

Mike Kaply

unread,
Aug 21, 2025, 12:42:49 PMAug 21
to Ruben Gomez, enter...@mozilla.org
Would you mind submitting one of the crashes and sending me the URL? When this happens, it's usually a background process crashing repeatedly.

You can do that from about:crashes

Thanks

Mike

--
You received this message because you are subscribed to the Google Groups "enter...@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email to enterprise+...@mozilla.org.
To view this discussion visit https://groups.google.com/a/mozilla.org/d/msgid/enterprise/e4909950-db12-4072-a137-44df2d0c3ceen%40mozilla.org.

Kasper, Ryan V. [US-US]

unread,
Aug 22, 2025, 1:10:12 PMAug 22
to Mike Kaply, Ruben Gomez, enter...@mozilla.org

Ruben/Mike,

 

I had to turn off QUIC (aka http3) after analyzing Wireshark for 140.2.0 traffic – specifically when searching  from new tab (engine=google)… Meant to bring this up and forgot, maybe it helps?

policies.json snippet:

{

  "policies": {

              "Preferences": {

                "network.http.http3.enable": {

                             "Value": false,

                             "Status": "locked"

                }

              }

  }

}

 

Thank you,

Ryan V. Kasper

 

From: 'Mike Kaply' via enter...@mozilla.org <enter...@mozilla.org>
Sent: Thursday, August 21, 2025 10:42 AM
To: Ruben Gomez <rigo...@gmail.com>
Cc: enter...@mozilla.org
Subject: EXTERNAL: Re: [Mozilla Enterprise] Re: Firefox ESR 140.2 crashhelper hanging process

 

Would you mind submitting one of the crashes and sending me the URL? When this happens, it's usually a background process crashing repeatedly. You can do that from about:crashes Thanks Mike On Thu, Aug 21, 2025 at 10:57 AM Ruben Gomez <rigomez88@gmail.com>

Mike Kaply

unread,
Aug 22, 2025, 1:14:56 PMAug 22
to Kasper, Ryan V. [US-US], Ruben Gomez, enter...@mozilla.org
Can you be more specific? What were you seeing?

Mike

Kasper, Ryan V. [US-US]

unread,
Aug 22, 2025, 2:40:38 PMAug 22
to Mike Kaply, Ruben Gomez, enter...@mozilla.org

Certainly,

 

I would open a new tab, type a search term in the nav bar, and it would just take forever to come back with anything.

 

Wireshark revealed:
xxx.xxx.xxx.xxx    192.178.155.106    QUIC    1294   

 

And I could tell that is where it was hanging and also that 192.178.155 is Google (1e100.net), so I tried disabling http3 and voila.

 

Thank you,

Ryan V. Kasper

 

From: Mike Kaply <mka...@mozilla.com>
Sent: Friday, August 22, 2025 11:15 AM
To: Kasper, Ryan V. [US-US] <Ryan.V...@leidos.com>
Cc: Ruben Gomez <rigo...@gmail.com>; enter...@mozilla.org
Subject: Re: EXTERNAL: Re: [Mozilla Enterprise] Re: Firefox ESR 140.2 crashhelper hanging process

 

Can you be more specific? What were you seeing? Mike On Fri, Aug 22, 2025 at 1:10 PM Kasper, Ryan V. [US-US] <Ryan.V.Kasper@leidos.com> wrote: Ruben/Mike, I had to turn off QUIC (aka http3) after analyzing Wireshark for 140.2.0 traffic

Reply all
Reply to author
Forward
0 new messages