summaryrefslogtreecommitdiff
path: root/libs/utils/ZipFileRO.cpp
diff options
context:
space:
mode:
author Chih-Chung Chang <chihchung@google.com> 2010-07-01 21:06:45 +0800
committer android-build SharedAccount <android-build@sekiwake.mtv.corp.google.com> 2010-07-15 14:59:25 -0700
commit2965922c1fec7a1a7e2812334e6a312038c9de0c (patch)
tree47ccdb5cc155f23e33b2fd1864018a9c8d2ea1e3 /libs/utils/ZipFileRO.cpp
parentd1ede1557188cde83a0220405b39905022f30581 (diff)
Flush binder buffer after setting raw heap to avoid leaking a reference.
The problem was: 1. In handleShutter(), thread A in CameraService calls registerBuffers(IMemoryHeap) and it's received by thread B in system_server. [transaction 1] 2. While thread A is waiting for the reply, thread B calls back to thread A to get the id of the heap (IMemoryHeap.getHeapID). [transaction 2] 3. Thread A replies transaction 2 and is preemptied in kernel. Thread B gets the reply and finishes registerBuffers and send reply for transaction 1. 4. When thread A runs again, it gets the reply for transaction 1 and returns to handleShutter(). 5. At this point the transaction buffer for transaction 2 (which holds a reference to IMemoryHeap) is not freed because the BC_FREE_BUFFER command is kept in thread A's local command queue and not sent to the kernel. 6. Normally when thread A makes next transaction, the BC_FREE_BUFFER command will be sent together (piggyback) with the commands for that transaction. But in this case thread A is a callback thread from camera driver, so it does not make any binder calls afterwards, and the IMemoryHeap is never freed (until the next time handleShutter is called). Change-Id: I435a258187509bdbbaf353339eb9ea577610cbd2
Diffstat (limited to 'libs/utils/ZipFileRO.cpp')
0 files changed, 0 insertions, 0 deletions