Closed
Bug 452064
Opened 16 years ago
Closed 16 years ago
TM: Hourly builds crash on javascript pages with JIT Content Enabled
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 452061
mozilla1.9.1a2
People
(Reporter: jmjjeffery, Unassigned)
References
Details
I went through several builds last night, hourly's and could not get any to start up as long as there was any pages with complex javascript; CNN/MSNBC etc... I gave up, went back to nightly and all was well. This morning I updated to today's nightly, all was well, but there was a couple of patches that landed post build that I wanted to test, so I downloaded the latest hourly... again Minefield will Crash with JIT Content enabled. So, seems to be something not working right in hourly that does in nightly... A config problem in the build machine ??? Using this hourly: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1a2pre) Gecko/20080825051210 Minefield/3.1a2pre Firefox/3.0 ID:20080825051210
Reporter | ||
Updated•16 years ago
|
Summary: TM: Hourly builds will not run with JIT Content Enabled → TM: Hourly builds crash on javascript pages with JIT Content Enabled
Comment 1•16 years ago
|
||
We need to jump on this. Is it the build process (say, busted dependencies? see bug 452061), or a recent change? /be
Comment 2•16 years ago
|
||
Yeah, I see the same when I have more than one extension installed and I try to open the add-ons window. It crashes with hourlies from the last few days but not with the latest nightly. Not sure if it is the same crash but it seems the same issue.
Reporter | ||
Comment 3•16 years ago
|
||
Hourly's no longer crash since fix for https://bugzilla.mozilla.org/show_bug.cgi?id=452061 was checked in. Using the latest hourly, no crashes, all extensions enabled, and a ages old profile... Marking this a dup of 452061 Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1a2pre) Gecko/20080825171121 Minefield/3.1a2pre Firefox/3.0 ID:20080825171121
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Comment 4•16 years ago
|
||
Actually simply touching the Makefile.in will cause its directory to be clobbered automatically so ideally you would wait to see whether another nanojit checkin affects the hourlies or not.
You need to log in
before you can comment on or make changes to this bug.
Description
•