MozillaZine

Problem starting Seamonkey

Discussion about Seamonkey builds
Post a reply
therube

User avatar
 
Posts: 6690
Joined: March 10th, 2004, 9:59 pm
Location: Maryland USA
November 7th, 2009, 9:48 am

Post Posted November 7th, 2009, 9:48 am

"incredible"

Not really.

2.0 is the "stable" branch.
2.1 is the development trunk.

It is intended to be that way so as not to have bugs on the branch & to find them on the trunk before the trunk branches.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.4) Gecko/20091017 SeaMonkey/2.0 Pinball Refspoof CopyURL+ FetchTextURL FlashGot NoScript
BANK OF AMERICA.COM ONLINE BANKING SUCKS IN THE HUGEST WAY IMAGINABLE
oorwullie

User avatar
 
Posts: 372
Joined: September 20th, 2005, 9:37 am
Location: Belfast NI
November 7th, 2009, 11:06 am

Post Posted November 7th, 2009, 11:06 am

4td8s wrote:
oorwullie wrote:Seems to be a problem with the extension JavaScript Debugger. Disabling this add-on will allow Seamonkey to start.


incredible that the Javascript Debugger addon (version 0.9.87.4) is the cause of the crashes for the SM 2.1a1pre nightly builds from 10/30. AND this is the same EXACT version of the Javascript Debugger addon included in SM 2.0 final.

time for that addon to be updated/revised to fix the crashes. so I expect newer nightly builds of SM 2.1a1pre to bundle newer versions of the Javascript Debugger extension.

Although disabling the debugger add-on is a work around, it is actually the Javascript engine that's at fault, according to Brendan Eich. Bug Comment 11
SM, TBird & FF trunk nightlies; Win XP sp3/Vista Home basic; OOo-dev 3.2
============================================
Creation
4td8s
 
Posts: 77
Joined: June 24th, 2009, 1:07 pm
November 8th, 2009, 8:55 am

Post Posted November 8th, 2009, 8:55 am

oorwullie wrote:Although disabling the debugger add-on is a work around, it is actually the Javascript engine that's at fault, according to Brendan Eich. Bug Comment 11


you mean the actual javascript engine in seamonkey 2.1a1pre nightly and not the javascript debugger addon. no wonder.
4td8s
 
Posts: 77
Joined: June 24th, 2009, 1:07 pm
November 9th, 2009, 12:10 pm

Post Posted November 9th, 2009, 12:10 pm

oorwullie & iav: the JS engine bug (bug no. 525544) has been fixed in Seamonkey 2.1a1pre nightly build of November 9. I installed that one on my Windows XP SP3 computer and the crashes are gone and can run SM 2.1a1pre normally instead of just running it in Safe Mode.

btw - bug no. 525481 only applies to Firefox/Minefield 3.7a1pre nightlies and that bug doesn't seem to occur in the Seamonkey 2.1a1pre nightlies I have tested. anyways, that bug has also been fixed in the latest FF/Minefield 3.7a1pre nightly builds.
oorwullie

User avatar
 
Posts: 372
Joined: September 20th, 2005, 9:37 am
Location: Belfast NI
November 9th, 2009, 3:58 pm

Post Posted November 9th, 2009, 3:58 pm

4td8s wrote:oorwullie & iav: the JS engine bug (bug no. 525544) has been fixed in Seamonkey 2.1a1pre nightly build of November 9. I installed that one on my Windows XP SP3 computer and the crashes are gone and can run SM 2.1a1pre normally instead of just running it in Safe Mode.

btw - bug no. 525481 only applies to Firefox/Minefield 3.7a1pre nightlies and that bug doesn't seem to occur in the Seamonkey 2.1a1pre nightlies I have tested. anyways, that bug has also been fixed in the latest FF/Minefield 3.7a1pre nightly builds.

Just downloaded today's nightly, enabled the JS Debugger and it is now WFM. Good news.
SM, TBird & FF trunk nightlies; Win XP sp3/Vista Home basic; OOo-dev 3.2
============================================
Creation
Previous

Return to SeaMonkey Builds

Post a reply

Who is online

Users browsing this forum: No registered users and 1 guest