Bug 23779 - Crash in WebCore::RenderObject::absoluteQuadsForRange when Inspect Element selected in context menu on image
Summary: Crash in WebCore::RenderObject::absoluteQuadsForRange when Inspect Element se...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (Deprecated) (show other bugs)
Version: 528+ (Nightly build)
Hardware: Macintosh PowerPC OS X 10.4
: P2 Critical
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2009-02-05 21:17 PST by Thomas Sutton
Modified: 2009-02-09 00:04 PST (History)
0 users

See Also:


Attachments
Crash report on 10.4.11 (26.66 KB, text/plain)
2009-02-05 21:18 PST, Thomas Sutton
no flags Details
Crash report on 10.5.6 (33.78 KB, text/plain)
2009-02-05 21:21 PST, Thomas Sutton
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Sutton 2009-02-05 21:17:13 PST
Right-clicking on an image and selecting "Inspect Element" crashes WebKit r40663. Repeatable every time on my iMac G5 running 10.4.11 and on my Macbook running 10.5.6. On both, the crash is in WebCore::RenderObject::absoluteQuadsForRange.

1) Start WebKit
2) Navigate to http://www.google.com.au/
3) Right-click on the Google logo
4) Select "Inspect Element"
5) Crash

Crash reports to come.
Comment 1 Thomas Sutton 2009-02-05 21:18:39 PST
Created attachment 27378 [details]
Crash report on 10.4.11
Comment 2 Thomas Sutton 2009-02-05 21:21:47 PST
Created attachment 27379 [details]
Crash report on 10.5.6
Comment 3 Thomas Sutton 2009-02-05 21:25:47 PST
Bringing up the Inspector (Command-I) and manually focusing on the image with the "select an element in the page to inspect it." button also crashes, in the same place.

So too does navigating the DOM tree in the inspector pane and selecting the <img> element.
Comment 4 Mark Rowe (bdash) 2009-02-05 21:34:21 PST
<rdar://problem/6562385>
Comment 5 Thomas Sutton 2009-02-09 00:04:17 PST
Reported by @webkit on Twitter <http://twitter.com/webkit/status/1191086640> as fixed in r40777.  After this update, I no longer see the crash.