Closed
Bug 662495
Opened 13 years ago
Closed 13 years ago
Crash at CheckStackAndEnterMethodJIT
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 595351
People
(Reporter: herbiedupree, Unassigned)
Details
(Keywords: crash, regression)
Crash Data
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 2nd crash in less than 24 hours for same problem. Also, the last 9 crashes have been prefaced by -bp. Reproducible: Sometimes Steps to Reproduce: 1.Last 2 Crash Reports 2. 3. Seems to be related to the JIT compiler and Javascript libraries. 0|1|mozjs.dll|CheckStackAndEnterMethodJIT|hg:hg.mozilla.org/releases/mozilla-2.0:js/src/methodjit/MethodJIT.cpp:fca718600ca0|778|0x23
Comment 1•13 years ago
|
||
Please go to about:crashes and paste links to the relevant crash reports here.
Assignee: nobody → general
Component: Page Info → JavaScript Engine
Keywords: crash,
stackwanted
Product: Firefox → Core
QA Contact: page.info → general
Version: unspecified → 2.0 Branch
(In reply to comment #1) > Please go to about:crashes and paste links to the relevant crash reports > here. https://crash-stats.mozilla.com/report/index/bp-4a0b4b67-6c57-4845-8328-6d4142110607
Comment 3•13 years ago
|
||
Setting dependency on Bug 595351
Blocks: SadJägerMonkey
Crash Signature: [@CheckStackAndEnterMethodJIT]
Keywords: stackwanted → regression
Summary: CheckStackAndEnterMethodJIT → Crash at CheckStackAndEnterMethodJIT
Comment 4•13 years ago
|
||
Without STR, this bug is considered as a dupe of bug 595351.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Comment 5•13 years ago
|
||
Bug 595351 is a metabug
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: DUPLICATE → ---
Comment 6•13 years ago
|
||
(In reply to comment #5) > Bug 595351 is a metabug The goal of a crash metabug is to track different causes per depending bug. What is the test case for this bug?
Comment 7•13 years ago
|
||
> The goal of a crash metabug is to track different causes per depending bug. Ah perhaps someone can update <https://bugzilla.mozilla.org/describekeywords.cgi#meta> because your use of meta isn't documented there. > What is the test case for this bug? No idea. I'm just helping out with triage.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → DUPLICATE
Comment 8•13 years ago
|
||
In the future, for bugs related to crashes, please use the [@ CrashSignature ] syntax in the summary so that it can be tracked in Socorro. For instance, see the "Bugzilla Ids" column in: https://crash-stats.mozilla.com/topcrasher/byversion/Firefox/4.0.1 Bugs related to crashes are classified as critical.
No longer blocks: SadJägerMonkey
Severity: normal → critical
Comment 9•13 years ago
|
||
Any time now server ops will be running a script to remove crash signatures from bug summaries. They are now supposed to go into the new crash signature field.
You need to log in
before you can comment on or make changes to this bug.
Description
•