WebKit2 UIProcess code should never use WebCore::Timer as it can lead to crashes. This is especially true for applications that make use of WK2 and WK1 at the same time. I tracked down a crash in a WebKit client to the use of WebCore::Timer in NavigationState.mm, which was introduced in https://trac.webkit.org/changeset/204716.
Created attachment 296753 [details] Patch
<rdar://problem/29360564>
Comment on attachment 296753 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=296753&action=review > Source/WebKit2/UIProcess/Cocoa/NavigationState.h:2 > - * Copyright (C) 2014 Apple Inc. All rights reserved. > + * Copyright (C) 2014-2016 Apple Inc. All rights reserved. Let's also #pragma once-ify this while we're here.
Created attachment 296754 [details] Patch for landing.
Created attachment 296755 [details] Patch for landing.
Comment on attachment 296755 [details] Patch for landing. Turning of CQ+ until tests complete.
Comment on attachment 296755 [details] Patch for landing. Ready to land.
Thank you for fixing.
Comment on attachment 296755 [details] Patch for landing. Clearing flags on attachment: 296755 Committed r209646: <http://trac.webkit.org/changeset/209646>
(In reply to comment #8) > Thank you for fixing. Any time! :)