Segmentation Fault with Captive Portal Setting Enabled

[ziproot]

When I go to about:preferences#privacy and, under "Icecat-specific privacy settings," enable the "Detect captive portal" setting, then close the browser, it does not reopen, instead giving a "segmentation fault." This is true in any profile including the default ones.

Steps to Reproduce:

1. Install latest icecat
2. Open icecat
3. In "about:preferences#privacy," under "Icecat-specific privacy settings," enable "Detect captive portal"
4. Close the browser
5. In a command line try to open icecat

Expected Result: Icecat opens normally and can detect captive portals.

Actual Result: Icecat refuses to open, saying "Segmentation Fault."

[losuler]

I had a look into this and quickly found that you definitely weren't alone with this issue^1^3, where I soon discovered that it's not (to my initial surprise) an issue with the changes in IceCat, but an upstream issue with Firefox^5, that appears was only just resolved a couple months ago^6. Sadly I think it's unlikely this will get backported to the ESR release, but if you like, I can look into backporting it for IceCat (the patch looks simple enough that it should be feasible).

[ziproot]

Sorry, I didn't realize it was a Firefox issue. I should have done more research before posting this bug. If this is a Firefox issue, then it's just a waiting game until IceCat updates to version 111 or later, so the next ESR release. I will keep this issue open until the update. Thank you for looking into that.

[carlosgonz0]

This Bug already fixed on 115.+ESR.

|| I can't reproduce this bug with recent Icecat (115.4.0esr, guix

Thanks