Bing causes crashes in 2.53.10

User Help for Seamonkey and Mozilla Suite
User avatar
ndebord
Posts: 1122
Joined: December 7th, 2002, 9:53 am

Re: Bing causes crashes in 2.53.10

Post by ndebord »

frg wrote:Nope. As I posted the crahs is in modules loading code and 2.57 also affected whichs till has the 60 ua. Can be mitigated by setting dom.moduleScripts.enabled to false but this will break other sites now working since 2.53.9
frg,

Won't be changing that setting to false, but will be using the Seamonkey and Firefox UA for now as that works with my bank where just SeaMonkey alone fails. uBlock seems to fix the Bing issue.

Nick
-N- Si vis pacem, para bellum
FrameWork, SeaMonkey(64-bit),Windows 10 Pro (X64- 21H2), WinPatrol, Malwarebytes & Panda Dome
User avatar
therube
Posts: 21703
Joined: March 10th, 2004, 9:59 pm
Location: Maryland USA

Re: Bing causes crashes in 2.53.10

Post by therube »

Seems to me this problem is caused by showing (new to 2.53.10) Firefox 68 in the UA string.
Nope. As I posted the crahs is in modules loading code and 2.57 also affected whichs till has the 60 ua.
(With only a 2 second test ... ;-) & aside from an actual crash in some particular module, it does appears the the code being served is affected by the UA, though the "key" to the UA issue looks not to be 60 vs 68, but rather 9 vs 10 (or I'm guessing, more generally 1 vs 2 digits in the last segment of [SeaMonkey] version number.)


So, this crashes:
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0 SeaMonkey/2.53.11
where this does not:
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0 SeaMonkey/2.53.9


(Wonder what's going to break once FF, in the not too distant future, hits 100.x.x ;-).
Fire 750, bring back 250.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript
User avatar
ndebord
Posts: 1122
Joined: December 7th, 2002, 9:53 am

Re: Bing causes crashes in 2.53.10

Post by ndebord »

therube wrote:
Seems to me this problem is caused by showing (new to 2.53.10) Firefox 68 in the UA string.
Nope. As I posted the crahs is in modules loading code and 2.57 also affected whichs till has the 60 ua.
(With only a 2 second test ... ;-) & aside from an actual crash in some particular module, it does appears the the code being served is affected by the UA, though the "key" to the UA issue looks not to be 60 vs 68, but rather 9 vs 10 (or I'm guessing, more generally 1 vs 2 digits in the last segment of [SeaMonkey] version number.)


So, this crashes:
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0 SeaMonkey/2.53.11
where this does not:
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0 SeaMonkey/2.53.9


(Wonder what's going to break once FF, in the not too distant future, hits 100.x.x ;-).
therube,

So, how do I change useragent from 10 to 9 when using 10?

TKs,
Nick
-N- Si vis pacem, para bellum
FrameWork, SeaMonkey(64-bit),Windows 10 Pro (X64- 21H2), WinPatrol, Malwarebytes & Panda Dome
User avatar
therube
Posts: 21703
Joined: March 10th, 2004, 9:59 pm
Location: Maryland USA

Re: Bing causes crashes in 2.53.10

Post by therube »

So, how do I change useragent from 10 to 9 when using 10?
The same as you would for any useragent change; by setting it in (or adding a site specific override in) general.useragent.bing.com, in this case.
Fire 750, bring back 250.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript
4td8s
Posts: 784
Joined: June 24th, 2009, 1:07 pm

Re: Bing causes crashes in 2.53.10

Post by 4td8s »

rdtom wrote:Bing loads okay for me.
me too - Bing site loads fine on my end with SM 2.53.10, no crashes
even with both ublock origin legacy & noscript 5.1.9 installed
NWKnight77
Posts: 22
Joined: November 12th, 2020, 6:09 pm

Re: Bing causes crashes in 2.53.10

Post by NWKnight77 »

I haven't checked this thread since the first two posts that dismissed the bug. The intent of the thread was to report a bug, so my job was done. I'll try the site specific override and see if it works. ...soon as I figure out how to do that again...

Edit: Changing user agents didn't seem to work*, but I turned on uBlock Origin for Bing and it seems to stop the script overload that crashes the browser.
*I probably should've restarted SeaMonkey
Post Reply