replicant-frameworks_native/libs
Eino-Ville Talvala 042ecee2ab CpuConsumer: Properly track acquired buffers
CpuConsumer cannot simply assume a slot's buffer is the same buffer
between acquire and release, and therefore it could be possible for
the same slot to get used for a second acquired buffer, if there's a
producer disconnect in between. This would cause a problem when the
first buffer is released by the consumer.

Instead, use an independent list of acquired buffers to properly track
their state.

Bug: 8291751
Change-Id: I0241ad8704e53d47318c7179b13daed8181b1fab
2013-03-05 15:25:06 -08:00
..
binder Fixes to native app ops services 2013-02-19 18:10:05 -08:00
cpustats Fix log spam about CPU frequency on one device 2012-05-14 16:55:26 -07:00
diskusage More changes to fix PDK build: 2012-10-24 12:30:41 -07:00
gui CpuConsumer: Properly track acquired buffers 2013-03-05 15:25:06 -08:00
ui Add createTJunctionFreeRegion 2013-02-27 11:13:03 -08:00
utils Revert "try to fix win_sdk build." 2013-02-02 18:09:15 -08:00