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)

defect
Not set
normal

Tracking

()

VERIFIED FIXED
mozilla1.0.1

People

(Reporter: marc.loiselle, Assigned: jst)

References

()

Details

(Keywords: crash, testcase, topcrash+)

Crash Data

Attachments

(2 files)

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.
Attached file testcase
Attachment #84266 - Attachment mime type: text/plain → text/html
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
*** 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. ***
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 → ---
Fix checked in.
Status: REOPENED → RESOLVED
Closed: 23 years ago23 years ago
Resolution: --- → FIXED
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.
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.
WFM with build 2002051006 under Windows ME.
Yup, this was intorduced on 5/17...
Adding [@ nsHTMLImageElement::GetImageFrame] to summary and keywords for future reference. This was a topcrash with recent MozillaTrunk builds.
Summary: Crash when trying to access complete property of Image → Crash when trying to access complete property of Image [@ nsHTMLImageElement::GetImageFrame]
*** Bug 145821 has been marked as a duplicate of this bug. ***
*** Bug 145711 has been marked as a duplicate of this bug. ***
wfm with buildid 2002052021 on linux.
v.fixed...no crashes in Talkback data since 5/20.
Status: RESOLVED → VERIFIED
Crash Signature: [@ nsHTMLImageElement::GetImageFrame]
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: