[DevTools] Fix a race between suspended and waiting messages in DevToolsSession
If a message comes right before navigation, and we send it out but never get a response from the old renderer (e.g. it was killed), and then suspend messages due to navigation, the original message is stuck in waiting_for_response_messages_ and will not be dispatched when resuming upon navigation finish. To mitigate this, we move all waiting messages to suspended if we are not resending them to new renderer due to being currently suspended. Bug: 803678 Change-Id: I125609e0ec8a5e2b98ff2d81a9e71732fc8f6f0f Reviewed-on: https://chromium-review.googlesource.com/887435Reviewed-by:Pavel Feldman <pfeldman@chromium.org> Reviewed-by:
John Chen <johnchen@chromium.org> Commit-Queue: Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#532307}
Showing
Please register or sign in to comment