| Issue 137: | Going back to mixare listview is causing a force close | |
| 1 person starred this issue and may be notified of changes. | Back to list |
Please use labels and text to provide additional information.
E/AndroidRuntime(11774): FATAL EXCEPTION: main
E/AndroidRuntime(11774): java.lang.RuntimeException: Unable to start activity ComponentInfo{org.mixare/org.mixare.MixListView}: java.lang.NullPointerException
E/AndroidRuntime(11774): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1768)
E/AndroidRuntime(11774): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1784)
E/AndroidRuntime(11774): at android.app.ActivityThread.access$1500(ActivityThread.java:123)
E/AndroidRuntime(11774): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:939)
E/AndroidRuntime(11774): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(11774): at android.os.Looper.loop(Looper.java:130)
E/AndroidRuntime(11774): at android.app.ActivityThread.main(ActivityThread.java:3835)
E/AndroidRuntime(11774): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(11774): at java.lang.reflect.Method.invoke(Method.java:507)
E/AndroidRuntime(11774): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:864)
E/AndroidRuntime(11774): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:622)
E/AndroidRuntime(11774): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime(11774): Caused by: java.lang.NullPointerException
E/AndroidRuntime(11774): at org.mixare.MixListView.onCreate(MixListView.java:90)
E/AndroidRuntime(11774): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
E/AndroidRuntime(11774): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1722)
E/AndroidRuntime(11774): ... 11 more
Jun 27, 2012
To reproduce, follow a link in listview that will cause the browser to be launched, then use the back button to go back to mixare.
Jun 27, 2012
Hi Daniele,
I think this has been already fixed,
and the fix on the development branch.
I tried to reproduce the issue, with the current development and I wasn't able to see the error.
In anycase, this is caused by "dead cycle" in dataView and MixContext, where is stored in MixView, mapView and listView; where MapView and ListView barely uses dataView.
I'm working on workFlow branch which should loose some of the coupling and document the code for future developers.
if the "mixare/development" has this issue too,
please add these lines in MixListView#onCreate() after super.onCreate()
Throwable tr = new Throwable();
Log.i("Mixare - Issue 137 ", "Intent= " + this.getIntent().getAction(), tr);
Regards,
Aug 7, 2012
(No comment was entered for this change.)
Status:
Fixed
|
Labels: -Priority-Medium Priority-High Version-AndroidRelease0.9