Re: [webkit-dev] DropAllLocks assertion on iOS (threading issue?)

Ok, I've created a new bug with the instruments trace here: https://bugs.webkit.org/show_bug.cgi?id=139654 I'll see what I can do about a sample project soon. I've also got a bit of new information to share. We released a new beta of the app in

Re: [webkit-dev] DropAllLocks assertion on iOS (threading issue?)

Can you attach the Instruments trace leading up to the crash, and/or a reduced copy of the app that can reproduce the crash, to bugzilla? Thanks, Geoff > On Dec 11, 2014, at 7:34 PM, Ian Ragsdale wrote: > > Actually, looking again, I was running the profile on the device, not the > simulator

Re: [webkit-dev] DropAllLocks assertion on iOS (threading issue?)

Actually, looking again, I was running the profile on the device, not the simulator as I had meant to. One other thing I meant to mention is that I keep three instances of the UIWebView loaded, and I trigger it by paging between them quickly, so perhaps it's an issue with multiple instances? Th

Re: [webkit-dev] DropAllLocks assertion on iOS (threading issue?)

Hi Geoff, thanks for the quick response! I don't believe I'm making any use of SPI, aside from whatever underlying use there is in UIWebView - I'm pretty sure that's not exposed to normal iOS apps (at least not that I'm aware of). As predicted, setting JSC_slowPathAllocsBetweenGCs does appear t

Re: [webkit-dev] DropAllLocks assertion on iOS (threading issue?)

Hi Ian. > From looking at the source, it tries to drop all locks from the current > javascript VM before calling the delegate, and when it does that it asserts > if the VM is busy garbage collecting. That’s right. > I'm guessing there needs to be some sort of guard there to make sure the VM >

[webkit-dev] DropAllLocks assertion on iOS (threading issue?)

Hello all, new member to the list, hopefully I'm in the right place. I'm using WebKit in an iOS app (via UIWebView), and we're seeing a semi-frequent crash that I'm trying to track down. From the backtraces, I _think_ it appears to be a WebKit bug, and so I'd like to try to find a workaround, a