diff options
| author | Catherine Liu <wlcl05@motorola.com> | 2012-06-27 15:11:04 -0700 |
|---|---|---|
| committer | Marcus Stojcevich <mstojcevich@gmail.com> | 2012-06-27 15:11:04 -0700 |
| commit | d96dab724b2655864f4e1cc761b0573fb00726b4 (patch) | |
| tree | 8b4db1367581ebccccf5ffbaf2bdbbe57f9b84cb /core/jni/android_os_MemoryFile.cpp | |
| parent | 44f9c784306665b040acab64b37aa514f8e22920 (diff) | |
| download | frameworks_base-d96dab724b2655864f4e1cc761b0573fb00726b4.zip frameworks_base-d96dab724b2655864f4e1cc761b0573fb00726b4.tar.gz frameworks_base-d96dab724b2655864f4e1cc761b0573fb00726b4.tar.bz2 | |
Fix sluggish to launch an app
The new trace feature/code in 4.0.4, which will dump the app stack
trace every 500ms if an app can't be launched within 500ms, is
holding the global ActivityManagerService lock unnecessarily. It
slows down the app's startup.
Change-Id: I91fbb043912b4d1fcf3e80d8ac4e61cd20ad89d1
Solution: move the trace file write operations out of sync block.
Diffstat (limited to 'core/jni/android_os_MemoryFile.cpp')
0 files changed, 0 insertions, 0 deletions