Closed Bug 30029 Opened 25 years ago Closed 25 years ago

startup crash

Categories

(Core :: JavaScript Engine, defect, P1)

Product:
Core
Component:
JavaScript Engine
Platform:
x86
All
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: jud, Assigned: jband_mozilla)

References

Details

(Whiteboard: [PDT+]) 

apparently random. I clobber built after seeing it the first-time. First startup 
of fresh NT build showed the same crash. I went back to get a stack trace and 
now it's gone.
I recall the crash in js_LockRuntime() and the profile code was in the stack.
Call stack is posted at 
news://news.mozilla.org/38BE5A06.23B5F736%40netscape.com. I see the same results 
exactly on Windows 2000. Jim Dunn's fix works here.
I see the same if I delete component.reg on linux. SO does slamm.

This is a tinderbox blocker.

Reassinging to jim dunn, elevating to blocker.
Assignee: nobody → jdunn
Severity: normal → blocker
OS: Windows NT → All
Priority: P3 → P1
The strange thing is that the shrike clobber build did not go orange until after
Jim's changes had cleared. Here's the link for the checkins when the tree went
orange,

http://bonsai.mozilla.org/cvsquery.cgi?module=SeaMonkeyAll&date=explicit&mindate=951962520&maxdate=951966539
jband has a fix; backing out my optimization fixes this. Jband is checking this
in.

Reassigning to jband.
Assignee: jdunn → jband
fix  checked in.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
*** Bug 30032 has been marked as a duplicate of this bug. ***
Putting on dogfood keyword, adding PDT+ for a quick verification.  Adding gbush 
on cc
Keywords: dogfood
Whiteboard: [PDT+]
*** Bug 30256 has been marked as a duplicate of this bug. ***
verified
Status: RESOLVED → VERIFIED
Mass removing self from CC list.
Now I feel sumb because I have to add back. Sorry for the spam.
You need to log in before you can comment on or make changes to this bug.