Brad Fitzpatrick 71678ddcc4 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
2010-10-28 13:51:58 -07:00
2010-10-28 12:29:15 -07:00
2010-10-27 16:13:59 -07:00
2010-10-19 16:56:02 -07:00
2010-10-19 16:56:02 -07:00
Description
No description provided
5.1 GiB
Languages
Java 77.3%
Kotlin 9.2%
PowerBuilder 6.6%
C++ 5.5%
AIDL 1%