Closed
Bug 145741
Opened 23 years ago
Closed 23 years ago
Crash when trying to access complete property of Image [@ nsHTMLImageElement::GetImageFrame]
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
VERIFIED
FIXED
mozilla1.0.1
People
(Reporter: marc.loiselle, Assigned: jst)
References
()
Details
(Keywords: crash, testcase, topcrash+)
Crash Data
Attachments
(2 files)
286 bytes,
text/html
|
Details | |
677 bytes,
patch
|
harishd
:
review+
|
Details | Diff | Splinter Review |
Buildid 2002051721 on Linux
A crash happens when javascript tries to access "complete" property of Image
javascript object. null should be returned.
I will attach a minimal testcase. The testcase comes from serverwatch.internet.com.
Reporter | ||
Comment 1•23 years ago
|
||
Assignee | ||
Updated•23 years ago
|
Attachment #84266 -
Attachment mime type: text/plain → text/html
Assignee | ||
Comment 2•23 years ago
|
||
This is a recent regression caused by the fix for bug 74091. Fix coming up.
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
OS: Linux → All
Hardware: PC → All
Target Milestone: --- → mozilla1.0.1
Assignee | ||
Comment 3•23 years ago
|
||
Comment 4•23 years ago
|
||
*** This bug has been marked as a duplicate of 145371 ***
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Comment on attachment 84288 [details] [diff] [review]
Don't call CallQueryInterface() on null pointers.
r=harishd
Attachment #84288 -
Flags: review+
*** Bug 145371 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 7•23 years ago
|
||
Oh, nice circular dupes! :-)
Reopening this one since the patch in the other bug is incorrect (fixes the
problem, but it incorrectly returns an error for a non-error case).
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Assignee | ||
Comment 8•23 years ago
|
||
Fix checked in.
Status: REOPENED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → FIXED
Comment 9•23 years ago
|
||
Just a note that the code before the Bug 74091's patch checked for the existence
of frame and returned a rv (which was probably *not* NS_OK). This patch returns
NS_OK. It shouldn't cause any problems, but I think it's worthy to note in case
some day it does.
Assignee | ||
Comment 10•23 years ago
|
||
That may be, but returning an error code from GetImageFrame() just because
there's no frame, is just wrong. The absense of a frame for that element is a
very normal case (as we've seen in the crash frequency that was caused by this
regression), it's not an error.
Comment 11•23 years ago
|
||
WFM with build 2002051006 under Windows ME.
Assignee | ||
Comment 12•23 years ago
|
||
Yup, this was intorduced on 5/17...
Comment 13•23 years ago
|
||
Adding [@ nsHTMLImageElement::GetImageFrame] to summary and keywords for future
reference. This was a topcrash with recent MozillaTrunk builds.
Comment 14•23 years ago
|
||
*** Bug 145821 has been marked as a duplicate of this bug. ***
Comment 15•23 years ago
|
||
*** Bug 145711 has been marked as a duplicate of this bug. ***
Reporter | ||
Comment 16•23 years ago
|
||
wfm with buildid 2002052021 on linux.
Comment 17•23 years ago
|
||
v.fixed...no crashes in Talkback data since 5/20.
Status: RESOLVED → VERIFIED
Updated•14 years ago
|
Crash Signature: [@ nsHTMLImageElement::GetImageFrame]
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
•