Closed Bug 332570 Opened 19 years ago Closed 19 years ago

Crash in e4x/XML/regress-324422-2.js windows js shell/browser

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Platform:
x86
Windows Server 2003
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 324533

People

(Reporter: bc, Unassigned)

References

Details

cloned from bug 324422 I am still crashing in the js shell on win2k3 at least. I don't have stacks with symbols unfortunately.
I no longer crash in the shell, but did crash in the browser with a 1.9a1_2006041523 build on win2k2, but could not reproduce with a 20060417 build on winxp. I'll wait to mark it wfm until the next run shows no crash.
still crashing... so not a wfm. test: e4x/XML/regress-324422-2.js result: FAILED type: shell : peachssh/2006-04-19-23-24-06-firefox-trunk-opt-1.9a1_2006041902.log : description: Expected exit code 0, got 5 Testcase terminated with signal 0 test: e4x/XML/regress-324422-2.js result: FAILED type: shell : peachssh/2006-04-20-03-19-43-firefox-trunk-dbg-1.9a1_2006041903.log : description: Expected exit code 0, got 5 Testcase terminated with signal 0 test: e4x/XML/regress-324422-2.js: result: CRASHED 5 (7.109000 seconds) type: browser description: none : peachssh/2006-04-19-23-24-06-firefox-trunk-opt-1.9a1_2006041902.log test: e4x/XML/regress-324422-2.js: result: CRASHED 5 (9.703000 seconds) type: browser description: none : peachssh/2006-04-20-03-19-43-firefox-trunk-dbg-1.9a1_2006041903.log
Summary: Crash in e4x/XML/regress-324422-2.js windows js shell → Crash in e4x/XML/regress-324422-2.js windows js shell/browser
finally got stacks and this is bug 324533 *** This bug has been marked as a duplicate of 324533 ***
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.