451865 - TM: startup crash, with Operator extension and content jit enabled @isPromoteInt(nanojit::LIns*)

Status: RESOLVED WORKSFORME

(Core :: JavaScript Engine, defect)

Description

[aja+bugzilla]

TM: startup crash @isPromoteInt(nanojit::LIns*), with Operator extension and content jit enabled

Comment 1

[aja+bugzilla]

FYI, without content jit enabled, the following is now showing up in error console

Error: Component is not available = NS_ERROR_NOT_AVAILABLE
Source file: chrome://operator/content/Microformats/Microformats.js
Line: 89

Comment 2

[aja+bugzilla]

In case it's relevant: Pentium 4 1.8GHz, which I guess makes it a Willamette, supporting MMX, SSE, and SSE2; running Ubuntu Hardy Heron 8.04 LTS. 

Comment 3

[aja+bugzilla]

Same on XP/SP3...changing OS to all, adding regression keyword

Comment 4

[aja+bugzilla]

WFM now, with an hourly after latest merge from tracemonkey branch to mozilla-central:

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b1pre) Gecko/20080902232545 Minefield/3.1b1pre ID:20080902232545

with content and chrome jit enabled.

Will verify on Ubuntu Hardy Heron shortly.

Comment 5

[aja+bugzilla]

WFM on Ubuntu Hardy Heron now, with nightly after latest merge from tracemonkey branch to mozilla-central:

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b1pre) Gecko/20080903020504 Minefield/3.1b1pre ID:20080903020504

WFM as in no more crash at startup with Operator extension and content and chrome jit enabled.

FYI, the following is now showing up in error console *with* jit enabled:

Error: Component is not available = NS_ERROR_NOT_AVAILABLE
Source file: chrome://operator/content/Microformats/Microformats.js
Line: 89

but that's another issue (although it apparently also regressed with initial jit landing on mozilla-central).

Comment 6

[(not currently active) Ted Mielczarek]

aja: are you sure that "Component is not available" is a TM problem, and not a dom quickstubs problem?

Comment 7

[aja+bugzilla]

(In reply to comment #6)
> aja: are you sure that "Component is not available" is a TM problem, and not a
> dom quickstubs problem?

Turns out this message is apparently only shown when Operator extension option "Show hidden microformats" is unchecked. I believe it's checked by default, and I must have unchecked it during problem determination for the crash.  Sorry about the irrelevant noise.

Comment 8

[Bob Clary [:bc] (inactive)]

no patch->wfm