Closed Bug 344137 Opened 18 years ago Closed 17 years ago

Crash in js1_5/extensions/regress-336409-[12].js, js1_5/extensions/regress-336410-[12].js

Categories

(Core :: JavaScript Engine, defect)

x86
Linux
defect
Not set
major

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: bc, Assigned: crowderbt)

References

Details

(Keywords: crash, Whiteboard: DUPEME)

js1_5/Regress/regress-336409-[12].js and js1_5/Regress/regress-336410-[12].js still crash in browser based tests on linux for 1.8.0.5, 1.8.1, 1.9. Since bug 336409 and bug 336410 are considered fixed, filing this bug to keep track of the crash. I'll try to debug more later. Marking sensitive (not a problem) since 336409 and 336410 are.
What stacks backtraces? Any other data? /be
Blocks: 344320
Ping? /be
(In reply to comment #2) I am in the process of downloading FC5 (although my FAP is causing me problems), I should have a local install of linux available no later than next week to be able to debug this better.
Bob, it is next week, currently ;) , can you still reproduce this bug?
They don't really crash per se, but exit with signal 6 SIGABRT. I can reproduce this on the qa farm linux machines running RHEL4 VMs as of 2006-08-07, but I can't reproduce the issue locally with FC5 VMs.
Dupe of bug 342790?
Whiteboard: DUPEME
Assignee: general → crowder
Status: NEW → ASSIGNED
Marking WFM unless bclary can still repro
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
yeah, looks fine on f8.
Group: security
Status: RESOLVED → VERIFIED
Summary: Crash in js1_5/Regress/regress-336409-[12].js, js1_5/Regress/regress-336410-[12].js → Crash in js1_5/extensions/regress-336409-[12].js, js1_5/extensions/regress-336410-[12].js
You need to log in before you can comment on or make changes to this bug.