Thanks Jon, I'll try that.

Goncalo Oliveira
Sent from my Windows Phone
From: Jonathan Pryor
Sent: 05-11-2012 20:34
To: Discussions related to Mono for Android
Subject: Re: [mono-android] Could not create epoll instance. errno=24
On Nov 5, 2012, at 9:51 AM, Goncalo Oliveira <[email protected]> wrote:
> Jon, that's after the crash occurred. There's no more information on the 
> crash itself.
>       ...
>       • 11-05 11:08:08.602: V/GpsLocationProvider(193): sv: 11 snr: 2.5 elev: 
> 9.0 azimuth: 242.0    U
>       • 11-05 11:08:08.616: A/Looper(5613): Could not create epoll instance.  
> errno=24
>       • 11-05 11:08:08.616: W/(5613): Thread 0x0 may have been prematurely 
> finalized
>       • 11-05 11:08:08.642: I/ActivityManager(193): Process Frotcom.FMobile 
> (pid 5613) has died.

Note that there are three different PIDs there, so the messages are
coming from three different processes. The GpsLocationProvider
messages can be ignored, on the assumption that pid 5613 is your
process (not that we can confirm that, as the logs don't go back far
enough). The pid 193 message is mostly ignorable; it's just letting us
know that process 5613 died.

What device are you running your app on? If possible, try running on a
Jelly Bean device; Jelly Bean copies application stderr to logcat,
which can provide a more complete view of what's going on.

Given that errno=24 is Too many open files (as you noted later in this
thread), it's likely that "elsewhere" in your app you're creating
something which deals with files, and it's not being collected until
your GC.Collect() call. I doubt that it's your callback code
allocating the instance, at least not in the callback code you
previously provided.

What _may_ help is enabling gref logging, and seeing which types are
collected during your callback GC.

        
http://docs.xamarin.com/Android/Guides/Deployment%2C_Testing%2C_and_Metrics/Diagnostics#Global_Reference_Messages

 - 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

Reply via email to