[Mono-bugs] [Bug 677250] New: Random null pointer exceptions when constantly re-creating the default activity (through screen rotation)

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Sun Mar 6 07:08:28 EST 2011


https://bugzilla.novell.com/show_bug.cgi?id=677250

https://bugzilla.novell.com/show_bug.cgi?id=677250#c0


           Summary: Random null pointer exceptions when constantly
                    re-creating the default activity (through screen
                    rotation)
    Classification: Mono
           Product: MonoDroid
           Version: unspecified
          Platform: x86-64
        OS/Version: Windows 7
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Runtime
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: matware at gmail.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: Beta-Customer
           Blocker: Yes


Description of Problem:
If I constantly rotate the device, causing the default activity to be
constantly recreated the application will eventually crash with a null pointer
exception.

Stack Trace :
I/MonoDroid( 7810): UNHANDLED EXCEPTION: Java.Lang.NullPointerException:
Exception of type 'Java.Lang.NullPointerException' was thrown.
I/MonoDroid( 7810): at Android.Runtime.JNIEnv.NewObject
(intptr,intptr,Android.Runtime.JValue[]) [0x00030] in
/home/jpobst/Desktop/mondroid/Mono.Android/src/Runtime/JNIEnv.cs:275
I/MonoDroid( 7810): at Android.Views.View..ctor (Android.Content.Context)
[0x00053] in
/home/jpobst/Desktop/mondroid/Mono.Android/platforms/android-8/src/generated/Android.Views.View.cs:1293
I/MonoDroid( 7810): at GraphView.GraphView..ctor
(Android.Content.Context,GraphView.SensorListener) [0x000b0] in
C:\Users\Matthew\Documents\Visual Studio
2010\Projects\GraphView\GraphView\Sensors.cs:272
I/MonoDroid( 7810): at GraphView.Sensors.OnCreate (Android.OS.Bundle) [0x0008c]
in C:\Users\Matthew\Documents\Visual Studio
2010\Projects\GraphView\GraphView\Sensors.cs:67
I/MonoDroid( 7810): at Android.App.Activity.n_OnCreate_Landroid_os_Bundle_
(intptr,intptr,intptr) [0x00010] in
/home/jpobst/Desktop/mondroid/Mono.Android/platforms/android-8/src/generated/Android.App.Activity.cs:1441
I/MonoDroid( 7810): at (wrapper dynamic-method)
object.ae7c4c6f-fd5f-4d41-b611-f3d71ff220ed (intptr,intptr,intptr) <IL 0x00012,
0x00033>
E/mono    ( 7810): [0xafd4a834:] EXCEPTION handling:
Java.Lang.NullPointerException: Exception of type
'Java.Lang.NullPointerException' was thrown.
E/mono    ( 7810): [0xafd4a834:] EXCEPTION handling:
Java.Lang.NullPointerException: Exception of type
'Java.Lang.NullPointerException' was thrown.
W/mono    ( 7810): exception inside UnhandledException handler: Exception of
type 'Java.Lang.NullPointerException' was thrown.

This issue appears to be more common in applications that allocate more memory.

Steps to reproduce the problem:
1. Build the attached application.
2. Rotate the device (watch the wiggly lines)
3. Everything will fall in a heap and there will be a null pointer exception.

Actual Results:
Crashing application

Expected Results:
..


How often does this happen? 
Depending on the amount of memory being allocated, between 5 rotations and 107
rotations.

Additional Information:

The attached app is probably be overcomplicated for just a test bed, but it's
what I've been using to play with Monodroid, so hey it's the best I've got
today.

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.


More information about the mono-bugs mailing list