| Summary: | WebContent crash in WebKit::WebPage::expandedRangeFromHandle | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Ryosuke Niwa <rniwa> | ||||||
| Component: | WebKit2 | Assignee: | Ryosuke Niwa <rniwa> | ||||||
| Status: | RESOLVED FIXED | ||||||||
| Severity: | Normal | CC: | barraclough, darin, ddkilzer, enrica, sam | ||||||
| Priority: | P2 | Keywords: | InRadar | ||||||
| Version: | 528+ (Nightly build) | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Attachments: |
|
||||||||
|
Description
Ryosuke Niwa
2014-10-23 14:38:08 PDT
Created attachment 240368 [details]
Fixes the crash
Committed r175143: <http://trac.webkit.org/changeset/175143> There is still one case that needs to be covered. Created attachment 240512 [details]
Additional fix
Comment on attachment 240512 [details] Additional fix View in context: https://bugs.webkit.org/attachment.cgi?id=240512&action=review > Source/WebKit2/ChangeLog:9 > + We must change that we have a valid currentRange before trying nit: s/change/check Committed revision 175235. Comment on attachment 240512 [details]
Additional fix
Do we know how all these nulls can happen? It's pretty easy to reproduce.
|