summaryrefslogtreecommitdiffstats
path: root/libs/rs/rsAllocation.cpp
diff options
context:
space:
mode:
authorBrad Fitzpatrick <bradfitz@android.com>2010-10-28 13:51:58 -0700
committerBrad Fitzpatrick <bradfitz@android.com>2010-10-28 13:51:58 -0700
commit71678ddcc45d9cd4557f3bed8bba5382bf36b68b (patch)
treee745071968b7845ff9f9bb29468e2a728865ead0 /libs/rs/rsAllocation.cpp
parent5164246d7e47b9c995ca1e1587f3056eb777f60b (diff)
downloadframeworks_base-71678ddcc45d9cd4557f3bed8bba5382bf36b68b.zip
frameworks_base-71678ddcc45d9cd4557f3bed8bba5382bf36b68b.tar.gz
frameworks_base-71678ddcc45d9cd4557f3bed8bba5382bf36b68b.tar.bz2
StrictMode: optimize common case (just dropboxing)
The way StrictMode is used during development, just dropboxing violations, could be a little more optimal, taking the ActivityManagerService call off the main thread. But we can only do this safely in the case where that's the only penalty. Data suggests this call, despite being async, still takes around 30 milliseconds. This isn't a major win, and arguably it might be a _better_ idea to slow down people's event loops more and further jank up their animations on violations, but I thought any less overhead from StrictMode, the better. Change-Id: Iad9cce1cb4a084fa64abc4b5e1b4f3bff6a08c94
Diffstat (limited to 'libs/rs/rsAllocation.cpp')
0 files changed, 0 insertions, 0 deletions