New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 614428 link

Starred by 1 user
Status: Duplicate
Merged: issue 570376
Owner: ----
Closed: May 2016
Cc:
█ nyquist@chromium.org
khushals...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Tapping on certain page elements can induce the compositor feature to send messages forever

Project Member Reported by kmarshall@chromium.org, May 24 2016 
Steps:
1. load www.google.com
2. press the application chooser icon (looks like a 3x3 grid in the top-right corner)
3. observe log spew on client or engine to see messages being transferred. The messages continue indefinitely.

Logs look something like this:
05-24 11:22:10.702  8335  8370 V chromium: [VERBOSE1:blimp_message_pump.cc(59)] Received <BlimpMessage type=COMPOSITOR render_widget_id=1 target_tab_id=0 byte_size=18>
05-24 11:22:10.702  8335  8370 V chromium: [VERBOSE2:blimp_message_demultiplexer.cc(33)] ProcessMessage : <BlimpMessage type=COMPOSITOR render_widget_id=1 target_tab_id=0 byte_size=18>
05-24 11:22:10.703  8335  8370 V chromium: [VERBOSE2:blimp_message_demultiplexer.cc(43)] Routed message <BlimpMessage type=COMPOSITOR render_widget_id=1 target_tab_id=0 byte_size=18>.
05-24 11:22:10.703  8335  8335 V chromium: [VERBOSE1:remote_channel_impl.cc(97)] Received commit request from the engine.
05-24 11:22:10.703  8335  8370 V chromium: [VERBOSE2:blimp_message_pump.cc(75)] OnProcessMessageComplete, result=0
05-24 11:22:10.704  8335  8370 V chromium: [VERBOSE2:blimp_message_pump.cc(42)] ReadNextPacket
05-24 11:22:10.704  8335  8370 V chromium: [VERBOSE2:stream_packet_reader.cc(80)] DoReadLoop (state=HEADER, result=0)
05-24 11:22:10.704  8335  8370 V chromium: [VERBOSE2:stream_packet_reader.cc(80)] DoReadLoop (state=HEADER, result=4)
05-24 11:22:10.704  8335  8370 V chromium: [VERBOSE2:stream_packet_reader.cc(80)] DoReadLoop (state=PAYLOAD, result=0)
05-24 11:22:10.704  8335  8370 V chromium: [VERBOSE2:stream_packet_reader.cc(80)] DoReadLoop (state=PAYLOAD, result=11)
05-24 11:22:10.704  8335  8370 V chromium: [VERBOSE2:blimp_message_pump.cc(53)] OnReadPacketComplete, result=24
05-24 11:22:10.704  8335  8370 V chromium: [VERBOSE1:blimp_message_pump.cc(59)] Received <BlimpMessage type=COMPOSITOR render_widget_id=1 target_tab_id=0 byte_size=24>
05-24 11:22:10.704  8335  8370 V chromium: [VERBOSE2:blimp_message_demultiplexer.cc(33)] ProcessMessage : <BlimpMessage type=COMPOSITOR render_widget_id=1 target_tab_id=0 byte_size=24>
05-24 11:22:10.704  8335  8370 V chromium: [VERBOSE2:blimp_message_demultiplexer.cc(43)] Routed message <BlimpMessage type=COMPOSITOR render_widget_id=1 target_tab_id=0 byte_size=24>.
05-24 11:22:10.705  8335  8335 V chromium: [VERBOSE1:remote_channel_impl.cc(140)] Received BeginMainFrameAborted from the engine with reason: CommitEarlyOutReason::FINISHED_NO_UPDATES
05-24 11:22:10.705  8335  8370 V chromium: [VERBOSE2:blimp_message_pump.cc(75)] OnProcessMessageComplete, result=0
05-24 11:22:10.705  8335  8370 V chromium: [VERBOSE2:blimp_message_pump.cc(42)] ReadNextPacket
05-24 11:22:10.705  8335  8370 V chromium: [VERBOSE2:stream_packet_reader.cc(80)] DoReadLoop (state=HEADER, result=0)
05-24 11:22:10.706  8335  8370 V chromium: [VERBOSE2:net_errors_posix.cc(19)] Error 11
05-24 11:22:10.708  8335  8335 V chromium: [VERBOSE1:remote_channel_impl.cc(451)] Sending BeginMainFrame request to the engine.
05-24 11:22:10.709  8335  8370 V chromium: [VERBOSE2:blimp_message_output_buffer.cc(64)] OutputBuffer::ProcessMessage <BlimpMessage type=COMPOSITOR render_widget_id=1 target_tab_id=0 byte_size=81>
05-24 11:22:10.709  8335  8370 V chromium: [VERBOSE1:blimp_connection.cc(66)] Sending <BlimpMessage type=COMPOSITOR render_widget_id=1 target_tab_id=0 byte_size=84>
05-24 11:22:10.709  8335  8370 V chromium: [VERBOSE2:stream_packet_writer.cc(83)] DoWriteLoop (state=HEADER, result=0)
05-24 11:22:10.709  8335  8370 V chromium: [VERBOSE2:stream_packet_writer.cc(83)] DoWriteLoop (state=HEADER, result=4)
05-24 11:22:10.709  8335  8370 V chromium: [VERBOSE2:stream_packet_writer.cc(83)] DoWriteLoop (state=PAYLOAD, result=0)
05-24 11:22:10.710  8335  8370 V chromium: [VERBOSE2:stream_packet_writer.cc(83)] DoWriteLoop (state=PAYLOAD, result=25)
05-24 11:22:10.710  8335  8370 V chromium: [VERBOSE2:blimp_connection.cc(92)] OnWritePacketComplete, result=0
05-24 11:22:10.710  8335  8370 V chromium: [VERBOSE2:blimp_message_output_buffer.cc(148)] Write complete, result=0
05-24 11:22:10.752  8335  8370 V chromium: [VERBOSE2:stream_packet_reader.cc(80)] DoReadLoop (state=HEADER, result=4)
05-24 11:22:10.752  8335  8370 V chromium: [VERBOSE2:stream_packet_reader.cc(80)] DoReadLoop (state=PAYLOAD, result=0)
05-24 11:22:10.752  8335  8370 V chromium: [VERBOSE2:net_errors_posix.cc(19)] Error 11
05-24 11:22:10.753  8335  8370 V chromium: [VERBOSE2:stream_packet_reader.cc(80)] DoReadLoop (state=PAYLOAD, result=11)
05-24 11:22:10.753  8335  8370 V chromium: [VERBOSE2:blimp_message_pump.cc(53)] OnReadPacketComplete, result=18
05-24 11:22:10.753  8335  8370 V chromium: [VERBOSE1:blimp_message_pump.cc(59)] Received <BlimpMessage type=COMPOSITOR render_widget_id=1 target_tab_id=0 byte_size=18>
05-24 11:22:10.753  8335  8370 V chromium: [VERBOSE2:blimp_message_demultiplexer.cc(33)] ProcessMessage : <BlimpMessage type=COMPOSITOR render_widget_id=1 target_tab_id=0 byte_size=18>
05-24 11:22:10.753  8335  8370 V chromium: [VERBOSE2:blimp_message_demultiplexer.cc(43)] Routed message <BlimpMessage type=COMPOSITOR render_widget_id=1 target_tab_id=0 byte_size=18>.
05-24 11:22:10.754  8335  8335 V chromium: [VERBOSE1:remote_channel_impl.cc(97)] Received commit request from the engine.
05-24 11:22:10.754  8335  8370 V chromium: [VERBOSE2:blimp_message_pump.cc(75)] OnProcessMessageComplete, result=0
05-24 11:22:10.754  8335  8370 V chromium: [VERBOSE2:blimp_message_pump.cc(42)] ReadNextPacket
05-24 11:22:10.754  8335  8370 V chromium: [VERBOSE2:stream_packet_reader.cc(80)] DoReadLoop (state=HEADER, result=0)
05-24 11:22:10.755  8335  8370 V chromium: [VERBOSE2:net_errors_posix.cc(19)] Error 11
05-24 11:22:10.755  8335  8370 V chromium: [VERBOSE2:stream_packet_reader.cc(80)] DoReadLoop (state=HEADER, result=4)
05-24 11:22:10.755  8335  8370 V chromium: [VERBOSE2:stream_packet_reader.cc(80)] DoReadLoop (state=PAYLOAD, result=0)
05-24 11:22:10.755  8335  8370 V chromium: [VERBOSE2:stream_packet_reader.cc(80)] DoReadLoop (state=PAYLOAD, result=10)
05-24 11:22:10.755  8335  8370 V chromium: [VERBOSE2:blimp_message_pump.cc(53)] OnReadPacketComplete, result=24
05-24 11:22:10.755  8335  8370 V chromium: [VERBOSE1:blimp_message_pump.cc(59)] Received <BlimpMessage type=COMPOSITOR render_widget_id=1 target_tab_id=0 byte_size=24>
05-24 11:22:10.756  8335  8370 V chromium: [VERBOSE2:blimp_message_demultiplexer.cc(33)] ProcessMessage : <BlimpMessage type=COMPOSITOR render_widget_id=1 target_tab_id=0 byte_size=24>
05-24 11:22:10.756  8335  8370 V chromium: [VERBOSE2:blimp_message_demultiplexer.cc(43)] Routed message <BlimpMessage type=COMPOSITOR render_widget_id=1 target_tab_id=0 byte_size=24>.
05-24 11:22:10.756  8335  8335 V chromium: [VERBOSE1:remote_channel_impl.cc(140)] Received BeginMainFrameAborted from the engine with reason: CommitEarlyOutReason::FINISHED_NO_UPDATES
05-24 11:22:10.756  8335  8370 V chromium: [VERBOSE2:blimp_message_pump.cc(75)] OnProcessMessageComplete, result=0

Comment 1 by kmarshall@chromium.org, May 24 2016

Components: Mobile>Blimp>Client

Comment 2 by khushals...@chromium.org, May 24 2016

Mergedinto: 570376
Status: Duplicate (was: Untriaged)
Did a little digging to confirm, this has got to do with not serializing animations on the engine.
Try this with ContentShell but don't push properties for the AnimationHost on the LayerTreeHost, https://code.google.com/p/chromium/codesearch#chromium/src/cc/animation/animation_host.h&l=79, and you'll see the same result.

Comment 3 by amineer@chromium.org, Dec 9 2016

Labels: Archive-Blimp
►

Sign in to add a comment