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

Issue 597743 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 589169
Owner:
Closed: Apr 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

The compositor messages should not be silently dropped on the engine.

Project Member Reported by khushals...@chromium.org, Mar 24 2016

Issue description

This patch increased the limit for max payload size: https://codereview.chromium.org/1823383002

In the cases where this limit is being crossed, we still need a clean way to give the user an indication of this error and reset the state of the affected features, rather than silently dropping the message, which can cause a deadlock since the compositor protocol currently assumes reliability of message delivery.
 
Summary: The compositor messages should not be silently dropped on the engine. (was: The compositor messages should not be silently dropped on the server.)

Comment 2 by w...@chromium.org, Apr 1 2016

Labels: OS-Linux
Suggest closing this out in favour of  issue 589169 , for now.
Mergedinto: 589169
Status: Duplicate (was: Assigned)
Sure, I'll merge it with that issue for now.
Labels: Archive-Blimp

Sign in to add a comment