summaryrefslogtreecommitdiff
path: root/rs/java/android/renderscript/ProgramFragmentFixedFunction.java
diff options
context:
space:
mode:
authorChalard Jean <jchalard@google.com>2019-05-30 14:58:29 +0900
committerChalard Jean <jchalard@google.com>2019-05-30 17:12:46 +0900
commitd5603307e1c453fdf8d2b65db1845d8c8ab48c28 (patch)
tree4038ed3704177668b934dc98355bf5c6f43bef00 /rs/java/android/renderscript/ProgramFragmentFixedFunction.java
parent969038422148973d02b276022f54921848618a46 (diff)
Prevent a 4-way binder interlock leading to a leak.
System server | NetworkStack | NetworkMonitorCallbacks ←----|--- NetworkMonitorCallbacks$Stub$Proxy ↓ | ↑ NetworkAgentInfo | NetworkMonitor ↓ | ↑ NetworkMonitor$Stub$Proxy ----|---→ NetworkMonitorImpl Bug: b/133174607 Test: Manual. The simplest artifact is observed by watching the output of adb shell dumpsys meminfo -d com.android.networkstack | grep 'Proxy Binders' while connecting and disconnecting multiple times to any network. This will display the number of binder proxies. Before this, the binder proxy count increases by 1 with each connection and never goes down (there is some noise, as proxy objects are sometimes created for other reasons, and get GC'd eventually). After this, the binder proxy count is always eventually stable at 27 + connected network count. See the bug for the complete analysis. Change-Id: Ide2428dab3fcd6d7cd00aa2a9fd99d6c99b815a4
Diffstat (limited to 'rs/java/android/renderscript/ProgramFragmentFixedFunction.java')
0 files changed, 0 insertions, 0 deletions