I don't understand why though... all the time seems to be taken up after the return from my ContentProvider.Query method.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jonathan Pryor Sent: Tuesday, November 20, 2012 5:50 PM To: Discussions related to Mono for Android Subject: Re: [mono-android] ContentResolver.Query takes greater than 10 seconds when returning while the actual DB query takes 4ms On Nov 20, 2012, at 5:23 PM, "Jeremy A. Kolb - ARA/NED" <[email protected]> wrote: > Actually it's hanging in: > > 0x12 in Android.Runtime.JNIEnv.CallObjectMethod at > /Users/builder/data/lanes/monodroid-mac-monodroid-4.2.7-branch/0e9eea34/source/monodroid/src/Mono.Android/src/Runtime/JNIEnv.g.vs:141 It wouldn't help much if you had it: IntPtr tmp = Env.CallObjectMethodA (Handle, jobject, jmethod, parms); It's the JNI CallObjectMethodA() function: http://docs.oracle.com/javase/1.5.0/docs/guide/jni/spec/functions.html#wp4309 We're calling into Java-land, and Java-land has decided to go on vacation for 10s until returning. JNI has some overhead, but not _that_ much overhead; the Java method you're invoking is doing something that's taking ~forever, and a Java caller would likely see the same thing. - Jon _______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid _______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
