Jon thanks for your fast reply.
Before the crash I see this in the log:
04-06 11:49:28.396 D/dalvikvm( 516): GREF has increased to 701
04-06 11:49:32.178 D/dalvikvm( 516): GREF has increased to 801
04-06 11:49:51.285 D/dalvikvm( 516): GREF has increased to 901
04-06 11:49:55.085 D/dalvikvm( 5
Jonathan Pryor-2 wrote
>
> I'm not sure where you're getting this sample from.
>
here: http://samples.xamarin.com/Samples/Details?type=MonoForAndroid&id=94
Alex
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Crash-on-list-scrolling-tp5620102p5622678.html
Sent
I get this error message periodically while calling 3rd party .jar library
method through handmade wrapper. After it application terminates.
---
Thread 0x0 may have been prematurely finalized
---
What does it mean? Looks like this happens suddenly without any reaso
On Apr 6, 2012, at 8:48 AM, gnauck wrote:
> here: http://samples.xamarin.com/Samples/Details?type=MonoForAndroid&id=94
Thanks; the sample was buggy, as it would constantly create new View instances
within Home_Adapter.GetView() instead of reusing the `convertView` parameter.
I've fixed this:
On Apr 6, 2012, at 8:44 AM, gnauck wrote:
> Each time I scroll down and up the list GREF increases and never goes down
> again. The same happens when I open the activity, go back and open it again
> several times.
>
> Is there a work around for this?
The work around is to Not Do That™. The Home
On Apr 6, 2012, at 11:37 AM, PVoLan wrote:
> I get this error message periodically while calling 3rd party .jar library
> method through handmade wrapper. After it application terminates.
>
> ---
> Thread 0x0 may have been prematurely finalized
I don't know where this is coming fr
Here is a bit more copypaste (MonetizationAPI is a part of library output,
just for beauty)
--
D/Mono: MonetizationAPI(31613): In Method: In Method: getLostMoneyCharged
D/Java: MonetizationAPI(31613): getLostMoneyCharged()
W/(31613): Thread 0x0 m
I am seeing the same problem. I am trying to bind the licensing libraries
from google. In addition to the warnings, I noticed that most of the types
are not imported by the binding generator. I'm not sure if this is related
to the warnings, but it is a show stopper for getting the licensing working
