SeaMonkey Browser Crash

User Help for Seamonkey and Mozilla Suite
Post Reply
Bluelead
Posts: 119
Joined: October 28th, 2009, 5:35 pm

SeaMonkey Browser Crash

Post by Bluelead »

In SeaMonkey, Preferences, Browser Start Up, window at bottom of page, I link to Bing.com. It seemed to work fine for a long time. Now when I use the "Browser" button on SeaMonkey's email page (lower left corner), it brings me to Bing, but SM crashes. When I use Bing independently of SM, Bing work well. I would like to use something other than Bing, such as Brave or Firebox. Right now I have had to go to Firefox to connect to MozillaZine. I am using Windows 7 with SM 2.5313 and Firefox 103.0, cookies allowed. Thank you!
frg
Posts: 1361
Joined: December 15th, 2015, 1:20 pm

Re: SeaMonkey Browser Crash

Post by frg »

as a temporary workaround set javascript.options.wasm to false. wasm is cr*p anyway.

FRG
User avatar
Peter Creasey
Posts: 1340
Joined: October 26th, 2007, 2:32 pm
Location: Texas

Re: SeaMonkey Browser Crash

Post by Peter Creasey »

frg wrote:as a temporary workaround set javascript.options.wasm to false. wasm is cr*p anyway.
Should all of us do this to reduce the script failure alerts that happen fairly often? Or is there a downside to doing this?

Thanks.
. . . . . . . . . . Pete
User avatar
therube
Posts: 21703
Joined: March 10th, 2004, 9:59 pm
Location: Maryland USA

Re: SeaMonkey Browser Crash

Post by therube »

Have you ever had the crash as described?
Have you tried what the OP described & did it crash on your end?
Are you apt to set things as the OP has?

What is the default value of "javascript.options.wasm"?
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
Bluelead
Posts: 119
Joined: October 28th, 2009, 5:35 pm

Re: SeaMonkey Browser Crash

Post by Bluelead »

I am sorry. I am just a novice to computing. Don't understand what I am suppose to do to fix the problem. Javascript is new to me.
hardys
Posts: 290
Joined: August 7th, 2015, 9:15 am

Re: SeaMonkey Browser Crash

Post by hardys »

Bluelead wrote: Don't understand what I am suppose to do to fix the problem.
- In the URL bar type about:config
- use the search to find javascript.options.wasm
- change the value from true to false by double click on the entry
- restart Seamonkey
User avatar
Peter Creasey
Posts: 1340
Joined: October 26th, 2007, 2:32 pm
Location: Texas

Re: SeaMonkey Browser Crash

Post by Peter Creasey »

as a temporary workaround set javascript.options.wasm to false. wasm is cr*p anyway.
Still wondering -- Should all of us do this to reduce the script failure alerts that happen fairly often? Or is there a downside to doing this?
. . . . . . . . . . Pete
User avatar
therube
Posts: 21703
Joined: March 10th, 2004, 9:59 pm
Location: Maryland USA

Re: SeaMonkey Browser Crash

Post by therube »

Should all of us do this to reduce the script failure alerts that happen fairly often?
No.
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
Peter Creasey
Posts: 1340
Joined: October 26th, 2007, 2:32 pm
Location: Texas

Re: SeaMonkey Browser Crash

Post by Peter Creasey »

Good to know -- thanks.
. . . . . . . . . . Pete
Bluelead
Posts: 119
Joined: October 28th, 2009, 5:35 pm

Re: SeaMonkey Browser Crash

Post by Bluelead »

That fixed my problem. I followed your instructions with "javascript.options.wasm to false." This is only a "temporary fix" What should I expect in the future? Thanks to all!
Post Reply