Closed
Bug 297002
Opened 20 years ago
Closed 18 years ago
crash when loading SVG with XMLHttpRequest
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: lpb+moz, Unassigned)
Details
(Keywords: crash, testcase)
Attachments
(3 files, 1 obsolete file)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050517 Firefox/1.0.4 (Debian package 1.0.4-2) Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050517 Firefox/1.0.4 (Debian package 1.0.4-2) When loading an SVG file using XMLHttpRequest, an exception is thrown; any subsequent attempts to use the XMLHttpRequest object crash the browser. Reproducible: Always Steps to Reproduce: 1. load the attached .xml file which attempts to load the attached .svg file. 2. 3. Actual Results: An alert shows the error in XMLHttpRequest.send(), and then the browser crashes. Expected Results: An alert should pop up with the text of the SVG file.
Comment 3•20 years ago
|
||
testcase loads svg from attachment 185610 [details]
Comment 4•20 years ago
|
||
in firefox 1.0.4 and trunk on winxpsp2 I don't crash but get Error: uncaught exception: [Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIXMLHttpRequest.status]" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: https://bugzilla.mozilla.org/attachment.cgi?id=185625 :: alertStruct :: line 36" data: no]
This updated test case by default loads directly from Bugzilla like Bob's test case. Improvements include: 1. No exception thrown in alertStruct, so you can get to the call to send() which is causing the problem/crash; 2. With the step-by-step reporting after the call to xhttp.send(), it's clear that at least on my machine Firefox will crash when attempting to access xhttp.responseText. Hope this helps.
Attachment #185609 -
Attachment is obsolete: true
After more testing, I can also say that using
xhttp.overrideMimeType("text/xml");
right before the call to xhttp.send(null) makes the crash go away. Is Firefox
looking at the .svg extension and trying to treat the XML content differently,
in a way to cause the crash? In a way that overriding the mime-type fixes?
Comment 7•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 8•19 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20051006 Firefox/1.4.1 ID:2005100614 wfm Can you reproduce with Firefox 1.5?
Updated•19 years ago
|
Comment 9•19 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8) Gecko/20060502 BonEcho/2.0a1 Testcase also WFM.
Comment 10•18 years ago
|
||
Testcase from comment #5 WFM Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.2pre) Gecko/20070205 BonEcho/2.0.0.2pre Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a2pre) Gecko/20070205 Minefield/3.0a2pre Some errors, but no crash.
Comment 11•18 years ago
|
||
-> wfm and no reply on comment 8 reporter: feel free to reopen if you can reproduce this bug with a current build/release
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
Updated•12 years ago
|
Component: DOM: Other → DOM
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•