Call SetActiveURL while handling IPCs on the *browser* side.
Knowing the URL is very helpful not only for diagnosing renderer crashes, but also for handling browser crashes, and DwoCs (e.g. ones issued for renderer kills). This CL introduces a call to ContentClient::SetActiveURL in 4 places in the browser process: - RenderViewHostImpl::OnMessageReceived - RenderFrameProxyHost::OnMessageReceived - RenderFrameHostImpl::OnMessageReceived - RenderFrameHostImpl::DidCommitProvisionalLoad Bug: 797968, 770239 Change-Id: I78481d0fcb40e7c0548eb5ee3bd1ff00c7703592 Reviewed-on: https://chromium-review.googlesource.com/846109 Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org> Reviewed-by:Alex Moshchuk <alexmos@chromium.org> Cr-Commit-Position: refs/heads/master@{#527031}
Showing
Please register or sign in to comment