Summary: | Inspecting an element in an Image Document causes an assertion failure (hit while inspecting Acid3) | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Sam Weinig <sam> | ||||||
Component: | Web Inspector (Deprecated) | Assignee: | Nobody <webkit-unassigned> | ||||||
Status: | RESOLVED FIXED | ||||||||
Severity: | Normal | CC: | ap, aroben, dev+webkit, eric, mitz, mrowe, timothy | ||||||
Priority: | P2 | Keywords: | InRadar | ||||||
Version: | 523.x (Safari 3) | ||||||||
Hardware: | All | ||||||||
OS: | All | ||||||||
Bug Depends on: | |||||||||
Bug Blocks: | 16755 | ||||||||
Attachments: |
|
Description
Sam Weinig
2007-06-20 20:45:32 PDT
Created attachment 15152 [details]
stack trace
Created attachment 15153 [details]
stack trace
This also happens with plugin documents, such as flash. *** Bug 16632 has been marked as a duplicate of this bug. *** The assertion failure results from calling FrameLoader::write(String) for a raw-data based document (an image) but ultimately to fix it one needs to know the expected behavior, i.e. what should the Inspector show in "source" view for non-text documents? I hit this just loading LexisNexis Academic search results. Since people are seeing this when inspecting Acid3 we might want to fix it sooner rather than later. (In reply to comment #8) > Since people are seeing this when inspecting Acid3 we might want to fix it > sooner rather than later. > I don't actually see a crash in a release build, just a blank panel where the view source should be. Actual assertion failure for bugzilla search posterity: SHOULD NEVER BE REACHED (/Users/matt/Code/WebKit/WebCore/loader/ImageDocument.cpp:91 virtual bool WebCore::ImageTokenizer::write(const WebCore::SegmentedString&, bool)) Seems to be fixed now. |