Bug 172509 - ASSERT(!m_timeoutTimer.isActive()) hit in BackgroundProcessResponsivenessTimer::responsivenessCheckTimerFired()
Summary: ASSERT(!m_timeoutTimer.isActive()) hit in BackgroundProcessResponsivenessTime...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit2 (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Chris Dumez
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2017-05-23 10:47 PDT by Chris Dumez
Modified: 2017-05-23 16:45 PDT (History)
6 users (show)

See Also:

Attachments
Patch (4.06 KB, patch)
2017-05-23 10:56 PDT, Chris Dumez 		ggaren: review+
Details | Formatted Diff | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Dumez 2017-05-23 10:47:55 PDT 
ASSERT(!m_timeoutTimer.isActive()) hit in BackgroundProcessResponsivenessTimer::responsivenessCheckTimerFired().
Comment 1 Chris Dumez 2017-05-23 10:48:16 PDT 
<rdar://problem/32251578>
Comment 2 Chris Dumez 2017-05-23 10:56:57 PDT 
Created attachment 311025 [details]
Patch
Comment 3 Geoffrey Garen 2017-05-23 16:35:25 PDT 
Comment on attachment 311025 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=311025&action=review

r=me

> Source/WebKit2/ChangeLog:28
> +        updateState() was called while the IPC handshake is doing on, we would have

is doing on => was in process
Comment 4 Chris Dumez 2017-05-23 16:45:47 PDT 
Committed r217307: <http://trac.webkit.org/changeset/217307>