| commit | 5f555569e757d280f707e2587b3d154c9d8c872f | [log] [tgz] |
|---|---|---|
| author | Jesse Hall <jessehall@google.com> | Thu Mar 07 15:14:18 2013 -0800 |
| committer | Jesse Hall <jessehall@google.com> | Thu Mar 07 15:21:26 2013 -0800 |
| tree | 469e6036650ba7ca592ef8b3f037fcaf7925647c | |
| parent | 78141e3acc9913153883fa337a0f3a5eff7acc64 [diff] |
When disconnecting a surface, cancel don't queue the buffer This isn't really right either, but avoids having an extra buffer that the consumer has to drain which it might not be expecting. To be correct, disconnecting a surface from a context should retain the current buffer and continue using it when reconnected. The buffer should only be canceled when the surface is destroyed. That will wait for a later change. Bug: 8320762 Change-Id: I5efa39c741193ca4f5612ea9de001ccbb683b345