Mathew Inwood 4985c5c782 Experimental: verify cached constructors before use.
Caching constructors can cause problems for dynamically loaded code if
the same class name appears in more than on classloader. Before using
cached constructors, verifty that they come from a valid classloader, i.e.
one that appears in the classloader chain of the current contexts
classloader. Remove ones that do not from the map to allow the associated
classes to be unloaded in case they're no longer in use.

Bug: 21690610
Change-Id: I84f2894cd03a5dc0c33aed9cd710e4a1f6d9515f
2015-12-31 12:32:40 +00:00
2015-12-16 13:47:14 -08:00
2015-12-14 12:04:26 -08:00
2015-12-09 11:20:32 -08:00
2015-12-18 13:12:58 -08:00
2015-12-30 18:17:30 +00:00
2015-12-30 22:34:12 +00:00
2015-11-23 23:16:04 +00:00
Description
No description provided
5.1 GiB
Languages
Java 77.3%
Kotlin 9.2%
PowerBuilder 6.6%
C++ 5.5%
AIDL 1%