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

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

Re: Crash with 136.0.2

Show all headers | View raw

On 23/03/2025 02:54, VanguardLH wrote:
> Jeff Layman <Jeff@invalid.invalid> wrote:
> 
>> As I mentioned above, Fx has been very stable and even if it has crashed
>> before it has been easy to restart. It's just because it wouldn't
>> restart this time that I posted here.
> 
> I noted back in "Updated Firefoxes for March 4th, 2025!" (Message-ID:
> <19xjxrw7dcxwu.dlg@v.nguard.lh>) that a restart of Firefox didn't work
> to apply the update to 136.  The Restart button didn't work, and I tried
> 3 times.  I was still at 135.  I had to exit Firefox and reload it to
> get it to move to 136.  That was the first time I hit a failure of an
> update to apply when clicking on Restart.
> 
> You noted here that Firefox 136 had a problem restarting after it
> crashed.  Hmm, seems something might be related between the two events.
> You can't check now after an OS restart, but if it happens again I would
> check Task Manager to see if all firefox.exe instances disappeared when
> you thought you exited Firefox.

Linux Mint has a similar program (System Monitor) to "Task Manager". I 
can check if there's anything Fx still running.

> There is a feature that lets service workers continue running in the
> background when you exit Firefox.  If you go to about:serviceworkers,
> you can see if any were started.  You can also go into Developer Mode
> (Ctrl+Shift+I), and look under the Application tab to see a list of
> registered service workers.
> 
> https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API
> 
> I have the feature disabled, so that page says "Service Workers are not
> enabled".  

My about:serviceworkers states "No Service Workers registered."

When I exit Firefox, I want it *all* immediately unloaded!
> There are also privacy issues with service workers since they can
> connect and stay connected after exiting Firefox.  You think your web
> session is finished when you exited Firefox, but service workers
> continue running in the background which means they can also continue
> sending data, like telemetry, plus they can make network connections
> that you don't know about since you didn't choose to visit there.

I have "Delete cookies and site data when Firefox is closed".

> https://www.chromium.org/Home/chromium-security/security-faq/service-worker-security-faq/
> 
> Service workers are not unique to Firefox.  Most web browsers support
> this feature.
> 
> https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API/Using_Service_Workers
> 
> https://hacks.mozilla.org/2014/06/serviceworkers-and-firefox/
> (c.2014)
>    "At their simplest, Service Workers are scripts that act as
>    client-side proxies for web pages. JavaScript code can intercept
>    network requests, deliver manufactured responses and perform
>    granular caching based on the unique needs of the application, a
>    feature that the web platform has lacked before now. This powerful
>    capability being made available to web developers enables, among other
>    things, the creation of fully-functioning offline experiences."
> 
> Mozilla again empowering web sites at the expense of security and
> privacy of their product users, but they probably just followed the pack
> in adding the feature.  Everyone else does it, so they did it, too.
> 
> To disable service workers in Firefox, change from True (default) to
> False the following setting in the about:config editor:
> 
> dom.serviceWorkers.enabled

Mine was "true". I've just toggled it to "false".

> Android users are caught unaware that exiting an app (its window
> disappears) does *not* unload the app until the OS decides it needs that
> memory for a newly loaded app, or until the user stops the app (via
> settings -> Apps -> <app> -> Stop, or using a task killer app).  It's
> how Android pretends it is faster at loading apps - by not unloading
> them figuring you're likely to soon reload the app.  Similarly, Firefox
> users are also often caught unaware that exiting its main window does
> not necessarily kill all of its processes.  Service workers can continue
> running, and be connecting out to somewhere you may not know about.

Yes, it's a "feature" of Android I can do without! I'm sure that Google 
makes use of it more than a little...

-- 
Jeff

Back to alt.comp.software.firefox | Previous | Next — Previous 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