Romain Guy 39fe17c8fb Cache drawable constant states instead of drawables
Bug #5678369

Caching drawables directly in a static map was responsible for runtime
restarts. If two different UI threads requested the same drawable, the
first thread to issue the request would be given a drawable callback
belonging to the second thread. This would cause an exception in
ViewRootImpl on invalidate.

The solution is to store the drawable states and to create a new
drawable instance every time a drawable is requested from the
cache. This is similar to how preloaded resources are handled.

Change-Id: I47e24e2a168cf67a3589185c6cd77b70f9a1c7cf
2011-11-30 10:34:07 -08:00
2011-11-15 16:12:30 -08:00
2011-11-21 18:05:04 -08:00
2011-11-15 14:21:58 -08:00
2011-11-28 17:56:02 -08:00
2011-11-23 16:26:13 -08:00
2011-11-18 16:57:21 -08:00
Description
No description provided
5.1 GiB
Languages
Java 77.3%
Kotlin 9.2%
PowerBuilder 6.6%
C++ 5.5%
AIDL 1%