Bug 57405

Summary: CrashTracer: 301 crashes in Safari at com.apple.WebCore: WebCore::AccessibilityRenderObject::visiblePositionForPoint const + 297
Product: WebKit Reporter: chris fleizach <cfleizach>
Component: AccessibilityAssignee: chris fleizach <cfleizach>
Status: RESOLVED FIXED    
Severity: Normal CC: bdakin, commit-queue
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: PC   
OS: OS X 10.5   
Attachments:
Description Flags
patch none

chris fleizach
Reported 2011-03-29 17:22:50 PDT
Thread 0 Crashed ↩: Dispatch queue: com.apple.main-thread 0 com.apple.WebCore 0x7fff869fb329 WebCore::AccessibilityRenderObject::visiblePositionForPoint(WebCore::IntPoint const&) const + 297 (/SourceCache/WebCore/ Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000038 Crashed Thread: 0 Dispatch queue: com.apple.main-thread WebCore-7533.20.24/accessibility/AccessibilityRenderObject.cpp:2557) 1 com.apple.WebCore 0x7fff86719c22 -[AccessibilityObjectWrapper accessibilityAttributeValue:forParameter:] + 2562 (/SourceCache/WebCore/WebCore-7533.20.24/accessibility/mac/AccessibilityObjectWrapper.mm:2360)
Attachments
patch (3.61 KB, patch)
2011-03-30 08:35 PDT, chris fleizach 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
chris fleizach
Comment 1 2011-03-29 17:23:11 PDT
That line is FrameView* frameView = m_renderer->document()->topDocument()->renderer()->view()->frameView(); which seems likely that there was a nil pointer in there somewhere
chris fleizach
Comment 2 2011-03-29 17:23:49 PDT
unfortunately, i can't reproduce this crash, and don't know how it occurs
chris fleizach
Comment 3 2011-03-30 08:35:34 PDT
Created attachment 87541 [details] patch
WebKit Commit Bot
Comment 4 2011-04-20 17:54:42 PDT
Comment on attachment 87541 [details] patch Clearing flags on attachment: 87541 Committed r84444: <http://trac.webkit.org/changeset/84444>
WebKit Commit Bot
Comment 5 2011-04-20 17:54:47 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.