Commit 42ceebee authored by Peter Marshall's avatar Peter Marshall Committed by Commit Bot

[inspector] Flush explicitly after sending resumed event

'resumed' events are sent to the renderer from V8 and stored in a queue.
We didn't flush this queue previously, meaning these events would sit in
the queue until another message coincidentally flushed the queue.

Under some circumstances, the resumed event would not get flushed and
the UI would still be in a paused state, even when JS had resumed.

Bug: chromium:1044989
Change-Id: I5d92fcc0a40d4e3816501da98f6be8a46f227e0f
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2023563Reviewed-by: 's avatarSimon Zünd <szuend@chromium.org>
Commit-Queue: Simon Zünd <szuend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#66041}
parent b9a690f3
...@@ -1665,6 +1665,7 @@ void V8DebuggerAgentImpl::didPause( ...@@ -1665,6 +1665,7 @@ void V8DebuggerAgentImpl::didPause(
void V8DebuggerAgentImpl::didContinue() { void V8DebuggerAgentImpl::didContinue() {
clearBreakDetails(); clearBreakDetails();
m_frontend.resumed(); m_frontend.resumed();
m_frontend.flush();
} }
void V8DebuggerAgentImpl::breakProgram( void V8DebuggerAgentImpl::breakProgram(
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment