Bug 175243

Summary: REGRESSION (iOS 11 beta 3): Microsoft Power BI crashes
Product: WebKit Reporter: erezg
Component: WebCore Misc.Assignee: Nobody <webkit-unassigned>
Status: RESOLVED WORKSFORME    
Severity: Major CC: ap, simon.fraser, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: Other   
Hardware: iPhone / iPad   
OS: iOS 11   
Attachments:
Description Flags
5 different crashes in WebCore none

erezg
Reported 2017-08-06 04:35:14 PDT
Created attachment 317360 [details] 5 different crashes in WebCore Hi. Since iOS 11 beta 3 came out, we've started to get crashes during a login flow involving UIWebView with a password box. Our app also has several WKWebViews preloaded and kept in memory for future use. We don't get these crashes when the WKWebViews aren't loaded (no loadRequest is called) Attached here is a ZIP with 5 crash examples (we get different ones). The crash usually happens when moving out of a password box and tapping a button. Main Thread stack traces tops: - WebCore::RenderBox::scrollPosition() - WebCore::RenderLayer::hitTestList - WebCore::LayoutState::LayoutState Web Thread stack traces tops: - WebCore::FontRanges::fontForFirstRange() (crash on overflow) - WebCore::RenderBlockFlow::estimateLogicalTopPosition Would appreciate your help. Thanks!
Attachments
5 different crashes in WebCore (153.09 KB, application/zip)
2017-08-06 04:35 PDT, erezg
no flags
Alexey Proskuryakov
Comment 1 2017-08-08 11:21:27 PDT
Does this crash in a more interesting way when using GuardMalloc or ASan (especially an ASan build of WebKit)?
Radar WebKit Bug Importer
Comment 2 2017-08-08 11:21:47 PDT
Simon Fraser (smfr)
Comment 3 2017-08-08 17:09:16 PDT
Best way to avoid these crashes would be to migrate to WKWebView.
erezg
Comment 4 2017-08-10 04:19:48 PDT
Looks like iOS 11 beta 5 handled all issues and I don't see these crashes anymore. I'll file another bug in case something pops up in future versions. Thanks!
Alexey Proskuryakov
Comment 5 2017-08-10 10:13:52 PDT
Thank you for following up!
Note You need to log in before you can comment on or make changes to this bug.