New issue
Advanced search Search tips

Issue 897327 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
danakj@chromium.org
samans@chromium.org
rjkroege@chromium.org
vmiura@google.com
piman@chromium.org
jonr...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Massive spew of failed CompositorFrameSink requests on navigation

Project Member Reported by fsam...@chromium.org, Oct 19 
I see A LOT of these dumped to console on navigation (say from slashdot.org to theverge.com).

[58221:58221:1019/172254.161204:ERROR:frame_sink_provider_impl.cc(34)] No RenderWidgetHost exists with id 29 in process 119
[58221:58221:1019/172254.161451:ERROR:frame_sink_provider_impl.cc(51)] No RenderWidgetHost exists with id 29 in process 119
[58221:58221:1019/172254.161650:ERROR:frame_sink_provider_impl.cc(34)] No RenderWidgetHost exists with id 22 in process 119
[58221:58221:1019/172254.161906:ERROR:frame_sink_provider_impl.cc(51)] No RenderWidgetHost exists with id 22 in process 119
[58221:58221:1019/172254.162112:ERROR:frame_sink_provider_impl.cc(34)] No RenderWidgetHost exists with id 14 in process 119
[58221:58221:1019/172254.162311:ERROR:frame_sink_provider_impl.cc(51)] No RenderWidgetHost exists with id 14 in process 119
[58221:58221:1019/172254.162527:ERROR:frame_sink_provider_impl.cc(34)] No RenderWidgetHost exists with id 11 in process 119
[58221:58221:1019/172254.162758:ERROR:frame_sink_provider_impl.cc(51)] No RenderWidgetHost exists with id 11 in process 119


Why are we requesting all these framesinks during navigation?

Comment 1 by danakj@chromium.org, Oct 19 

Is it possible to get some kinda stack trace or logging from the renderer? Are we making new widgets, swapping them in, or something?

Comment 2 by fsam...@chromium.org, Oct 19 

I did some logging from the renderer. It looks like this is the second time we're requesting a FrameSink for a given FrameSinkId. I think we're probably swapping in but I need to put in more logging.

Comment 3 by fsam...@chromium.org, Oct 19 

Weird, I don't see RenderWidget::SetSwappedOut getting called for the given FrameSinkId. I'm not sure what's going on. We just seem to be requesting FrameSinks twice. I wonder if on teardown we drop the CompositorFrameSink which causes cc to request another?
►

Sign in to add a comment