Closed Bug 314059 Opened 20 years ago Closed 20 years ago

crash [@ XMLToXMLString] (jsxml.c line 2867)

Categories

(Core :: JavaScript Engine, defect, P1)

x86
Windows XP
defect

Tracking

()

VERIFIED FIXED
mozilla1.8rc1

People

(Reporter: Seno.Aiko, Assigned: mrbkap)

Details

(Keywords: crash, testcase, verified1.8)

Crash Data

Attachments

(2 files)

This is similar to bug 311580, it creates a huge XML object and tries to stringify it. Open the attached testcase, then press the button (or, in the JS shell, type 'body'). This probably crashes. I suck at using WinDbg (and debugging C in general), but it points to this line: if (ns->prefix && !IS_EMPTY(ns->prefix)) { where ns is an invalid but non-null pointer, causing an access violation. Btw., thank you for the Bugzilla permissions. I'll leave this report unconfirmed until somebody else can reproduce it. (Build id: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051027 Firefox/1.6a1)
Attached file testcase —
confirm on branch and trunk/winxp
Severity: normal → major
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: testcase?
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051027 Firefox/1.5 I am confirming too.
Attached patch Fix — — Splinter Review
This has r=brendan. We are int-tagging the marks, but not int-detagging them to use them.
Assignee: general → mrbkap
Status: NEW → ASSIGNED
Attachment #201069 - Flags: review+
Attachment #201069 - Flags: approval1.8rc1?
One-line patch to a bug that leaves a dangling pointer being used for loads but not stores. Probably not exploitable, easily fixed, E4X polish bug. Should ride along if there is an rc2. /be
Flags: blocking1.8rc1?
Checked into trunk.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Severity: major → critical
Priority: -- → P1
Target Milestone: --- → mozilla1.8rc1
Status: RESOLVED → VERIFIED
(In reply to comment #5) > One-line patch to a bug that leaves a dangling pointer being used for loads but > not stores. Probably not exploitable, easily fixed, E4X polish bug. Should > ride along if there is an rc2. > > /be > We absolutely need a RC2 I crashed a lot these past 2 days. It started with 20051016 daily. TB11144987H I'm trying to figure out what caused this and maybe open a bug. I was too busy at College.
moving out to the 1.8 rc2 ride-along candidate list. We'll consider taking this if we do an RC2.
Flags: blocking1.8rc1? → blocking1.8rc2?
Attachment #201069 - Flags: approval1.8rc1? → approval1.8rc1+
Checked into MOZILLA_1_8_BRANCH.
Keywords: fixed1.8
Flags: blocking1.8rc2? → blocking1.8rc2+
tested with firefox 1.5 rc2 on winxp/linux testcase: no crash, out of memory in js console
Keywords: fixed1.8 → verified1.8
can't really add to the automatic tests since it requires a user action after the out of memory error which I can't catch.
Flags: testcase? → testcase-
Crash Signature: [@ XMLToXMLString]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: