Just to support the original thread, my problematic device is Android 2.2
GM10 MID.
Is there any chance this limit can be disabled in runtime? F.e. with
adb shell setprop dalvik.vm.checkjni false
Can somebody try this? (I have no access to the device now)
Igor
On Fri, Feb 3, 2012 at 7:55 PM
Thanks, this worked.
Was wondered that there is no difference between
System.IDisposable.Dispose() and Java.Lang.IDisposable.Dispose() for GREF
collecting.
As long as e.Values is not a Java object anyway, this seemed wonderful that
it can create GREF. Now I know the truth. (=
--
View this messa
On Feb 3, 2012, at 10:28 AM, Wally McClure wrote:
> Not to interject to much into this conversation, but I am fearful of calling
> GC.Collect() automatically too much. For example, I find the magnetic field
> sensor to basically take over my htc evo when I am getting change events. I
> realize
marin to explain the intricacies of the Mono
for Android GC?
Wally
> From: j...@xamarin.com
> Date: Fri, 3 Feb 2012 10:00:22 -0500
> To: monodroid@lists.ximian.com
> Subject: Re: [mono-android] Excessive JNI global references (2001) on hardware
>
> On Feb 3, 2012, at 7:54 AM, P
On Feb 3, 2012, at 7:54 AM, PVoLan wrote:
> Please, look at this test case https://github.com/PVoLan/TestAccelerometer
Your sample is is largely a simplified version of:
http://bugzilla.xamarin.com/show_bug.cgi?id=1084
The current "fix" (workaround) is to dispose of `val` within
SensorL
Please, look at this test case
https://github.com/PVoLan/TestAccelerometer
Try to launch it anywhere with working accelerometer and GREF limit 2000.
Here is a result of launching it on my Tablet LUNA RMD 7 with Android 2.3.1
*
I/-(1
On Feb 2, 2012, at 2:58 AM, PVoLan wrote:
> Catched same problem at:
>
> Tablet LUNA RMD 7 with Android 2.3.1
> Phone Samsung GT-I5700 with Android 2.2.2 (firmware was updated by user from
> original 2.1)
What I find incredible is that there is shipping hardware with the emulator
limits enabled
HTC Wildfire with Android 2.2.1 (original) worked properly
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Excessive-JNI-global-references-2001-on-hardware-tp5081943p5450413.html
Sent from the Mono for Android mailing list archive at Nabble.com.
Catched same problem at:
Tablet LUNA RMD 7 with Android 2.3.1
Phone Samsung GT-I5700 with Android 2.2.2 (firmware was updated by user from
original 2.1)
Can provide a testcase if needed.
Will test on device with original firmware and report later.
--
View this message in context:
http://mono-f
On Dec 16, 2011, at 10:06 PM, Igor Russkih wrote:
> I'm using a noname android tablet (2.2) for testing, and found that it often
> gives me E/dalvikvm( 519): Excessive JNI global references (2001)
Your tablet is "broken" and is using the emulator image. (Why on earth is it
doing that?)
I have n
This is set low for debugging it means there are native resources being
allocated which are not being freed - You can turn this off using...
adb.exe shell setprop dalvik.vm.checkjni false
however - *you dont want to!!*
it means there is almost certainly a serious leak, and I bet in your case it
Hello,
I'm using a noname android tablet (2.2) for testing, and found that it
often gives me
*E/dalvikvm( 519): Excessive JNI global references (2001)*
Is there any information why the limit can be so low on the device and if
this could be reconfigured somehow?
Is there any information on other
12 matches
Mail list logo
