Add debugging info for software compositor swap.

Add debugging info for software compositor swap.

The ReceivedBadMessage has been getting hit in the wild, so add some extra histograms and CHECKS to try to find out why.

BUG=
R=piman@chromium.org

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=230532

[piman, 2013-10-23 00:10:14]

lgtm

https://codereview.chromium.org/35883006/diff/1/content/browser/renderer_host...
File content/browser/renderer_host/render_widget_host_view_aura.cc (right):

https://codereview.chromium.org/35883006/diff/1/content/browser/renderer_host...
content/browser/renderer_host/render_widget_host_view_aura.cc:1591:
host_->GetProcess()->ReceivedBadMessage();
TBH this could fail if we're out of address space (or file descriptors - you may
want to add one more check, before this, on the handle) in the browser. I'm not
sure killing the renderer is the right thing to do in this case, but again, we
can't really do anything good either way :(

[jbauman, 2013-10-23 00:25:09]

On 2013/10/23 00:10:14, piman wrote:
> lgtm
> 
>
https://codereview.chromium.org/35883006/diff/1/content/browser/renderer_host...
> File content/browser/renderer_host/render_widget_host_view_aura.cc (right):
> 
>
https://codereview.chromium.org/35883006/diff/1/content/browser/renderer_host...
> content/browser/renderer_host/render_widget_host_view_aura.cc:1591:
> host_->GetProcess()->ReceivedBadMessage();
> TBH this could fail if we're out of address space (or file descriptors - you
may
> want to add one more check, before this, on the handle) in the browser. I'm
not
> sure killing the renderer is the right thing to do in this case, but again, we
> can't really do anything good either way :(

Yeah, I'm thinking of getting rid of that one in the future, but for now I'd
like to know whether that's actually happening. I can't really understand why
the browser process would be running out of address space, unless there are
issues with memory fragmentation.

[commit-bot: I haz the power, 2013-10-23 00:27:43]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/jbauman@chromium.org/35883006/1

[commit-bot: I haz the power, 2013-10-23 01:39:01]

Retried try job too often on linux_aura for step(s) content_unittests
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=linux_aura...

[jbauman, 2013-10-23 22:45:56]

Committed patchset #2 manually as r230532 (presubmit successful).