Repository navigation
The Java.Interop.TypeManager static constructor allocates lots of strings #1829
Description
When recently profiling Xamarin.Android application startup, we observed that lots of strings were being allocated by the Java.Interop.TypeManager static constructor.
These are probably coming from the __TypeRegistrations.RegisterPackages() call: https://github.com/xamarin/xamarin-android/blob/bb8183c8c16667b18ba9197e78294b17a0af532c/src/Mono.Android/Java.Interop/TypeManager.cs#L34
That's from a generated file; src/Mono.Android/obj/Debug/android-27//mcw/Java.Interop.__TypeRegistrations.cs partially contains:
partial class __TypeRegistrations {
public static void RegisterPackages ()
{
#if MONODROID_TIMING
var start = DateTime.Now;
Android.Util.Log.Info ("MonoDroid-Timing", "RegisterPackages start: " + (start - new DateTime (1970, 1, 1)).TotalMilliseconds);
#endif // def MONODROID_TIMING
Java.Interop.TypeManager.RegisterPackages (
new string[]{
"android",
"android/accessibilityservice",
"android/gesture",
// ...
},
new Converter<string, Type>[]{
lookup_android_package,
// ...
});
#if MONODROID_TIMING
var end = DateTime.Now;
Android.Util.Log.Info ("MonoDroid-Timing", "RegisterPackages time: " + (end - new DateTime (1970, 1, 1)).TotalMilliseconds + " [elapsed: " + (end - start).TotalMilliseconds + " ms]");
#endif // def MONODROID_TIMING
}Can all of the strings in here be avoided (type maps?) or deferred until laster so it's not part of process startup?
VS bug #635224
Activity
jonpryor commentedon Jul 2, 2018
On further thought, the
typemap.mjandtypemap.jmfiles suggest that__TypeRegistrations.RegisterPackages()shouldn't be needed at all. Removing them entirely -- or at least not calling them -- should help with the strings allocated and overall startup time.jonathanpeppers commentedon Feb 18, 2026
__TypeRegistrationsis no longer used, I think this is old and can be closed.