Is Bing crashing on latest stable a known problem?

I did a useragent override and told bing.com that SeaMonkey is Safari on a Mac and reloaded and everything works.

DaemonFC: what do you mean by "Bing crashing"?

DaemonFC: I presume Bing causing SeaMonkey to crash? I've not seen reports but I don't look at every forum and tend to avoid using Bing myself

DaemonFC: I think Bing.com is seeing the Firefox in the UA and serving something that causes SeaMonkey to choke

Yeah, basically load Bing.com and do anything with the page and all of SeaMonkey crashes.

The way I understand it, SeaMonkey is using Gecko 60.8 and lying about being Firefox 78 so that sites will let it in anyway.

But then you risk having them send content SeaMonkey doesn't support and crashing it.

IanN_Away DaemonFC: I think Bing.com is seeing the Firefox in the UA and serving something that causes SeaMonkey to choke

Microsoft Web sites are particularly nasty.

I tried stepping through their Outlook, Live, Office mess to see why it was sending GNOME Web to a fallback page meant for Internet Explorer 6 a few years ago, and then we just gave up and called it.

(When I went to check my Webmail. I just use IMAP now on everything and completely ignore their Web site.)

Lying to Bing.com and saying IE 11 on Windows 10 stops it from crashing, but then you get "Unsupported Browser". "Safari on Mac" (latest version) works.

DaemonFC: when I get chance I'll attach something like gdb and see what the trace looks like

DaemonFC: it is somewhere between Gecko 60.8 and 78, trouble is there is stuff in 60.x we want to keep which was removed by 78 so we cannot just switch to the 78 backend

So this is turning into another Goanna or something?

I haven't paid attention to SeaMonkey in years, but noticed Fedora packages it.

Ubuntu deleted it ahead of Debian a long time ago.

i think they struggled to get a maintainer

That's never stopped them before.

Usually they just shove things into Universe and say security problems piling up aren't a problem because it's not in Main. :)

maybe that was a different distro, maybe somewhere there is information about why it was dropped

You can get it. There's this thing called UbuntuZilla or something on SourceForge. It's and Apt repo. I didn't look into it because an Apt repo on SourceForge sounds super sketchy.

anyway, i'm off to work, bbl

bing crash is deep in modules loading code. Setting javascript.options.wasm to false helps. If you use uBlock and NoScript also no crash. I didn't find a direct bug with a patch attached which would fix it but should go away with more backports to either wasm or SpiderMonkey. Suspect something with unsupported dynamic module loading.

frg_Away: I still think you guys should abandon the 56 and 60 lines and side with me to evolve the Aura Runtime Environment.. specifically on a project to uplift the JS engine wholesale as high as we can possibly go

tho my goals may not align with what SeaMonkey wants to do in the end.. other than fade away of course.. Seeing as I am working to transform the pseudo-firefox platform BACK into a communicator platform.. XPFE 2.0!

or was that toolkit lol

still communicator design!

at BinOC 2022 looks a lot like 2002!

less twos but superior ux

what we need is to kill Google, not to evolve any platform

sadly I fear that that ship has sailed

at this stage of my life I don't want any more change

Speaking of sites that make SeaMonkey choke, I've been reading the news by pointing SeaMonkey at NewsWaffle through a Gemini to Web proxy.

I bookmarked that so that it strips down the news sites to just the text (as GemText) and then the proxy takes the GemText and converts it back to a very simple HTML that I can read without SeaMonkey not doing so very well with it.

The NewsWaffle is just a CGI program. I suppose that someone could convert it to run on a Web site directly, or maybe even integrate it into a Web browser so it fetches the crap, throws everything but the text out, and presents the text.

It not only busts through all the paywalls, but stops the ads, in page pop-ups, JavaScript, formatting, etc. So there's like almost no processing. It's faster to send it through Gemini, convert it, send it to another site that acts as a Gemini proxy, and on to the browser, than it is to load the site directly. I'm considering setting up a local proxy that handles Gemini requests to cut out...

...the last step and use Geminispace directly from SeaMonkey.

just found a website using AVIF images

wtf is an AVIF?

simpleflying.com/albastar-wheeltug-european-launch-customer top headline image is an AVIF

of course that won't render on SeaMonkey, but WTF they used AVIF in first place!?

oh, so someone reusing video codecs to encode still images. WHY.