Crash when starting tomdroid this afternoon

Bug #1040581 reported by Biji
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Tomdroid
Incomplete
High
Unassigned

Bug Description

Using latest bzr update
Tomdroid crash just after it started, maybe when trying to restore instance?

Revision history for this message
Biji (biji) wrote :

Logcat

Revision history for this message
Stefan Hammer (j-4-deactivatedaccount) wrote :

can you also send the top of the log please, I think there is something important missing :-)

Revision history for this message
Stefan Hammer (j-4-deactivatedaccount) wrote :

maybe even as text if possible?! and please also send the things below...

Revision history for this message
Biji (biji) wrote :

I can not reproduce the error :)
It was null pointer exception

Revision history for this message
Stefan Hammer (j-4-deactivatedaccount) wrote :
Download full text (3.9 KiB)

I could reproduce this (rarely)
Just do something with Tomdroid... wait for a long, long time (force stop does not help) and eventuelly, when starting Tomdroid this happens:

08-23 16:11:05.093: I/ActivityManager(140): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=org.tomdroid/.ui.Tomdroid bnds=[245,231][355,349] } from pid 4561
08-23 16:11:05.133: I/ActivityManager(140): Start proc org.tomdroid for activity org.tomdroid/.ui.Tomdroid: pid=11004 uid=10047 gids={3003, 1015}
08-23 16:11:05.203: V/RenderScript_jni(4561): surfaceDestroyed
08-23 16:11:05.273: I/ActivityThread(11004): Pub org.tomdroid.notes: org.tomdroid.NoteProvider
08-23 16:11:05.303: I/ActivityThread(11004): Pub org.tomdroid.util.SearchSuggestionProvider: org.tomdroid.util.SearchSuggestionProvider
08-23 16:11:05.413: D/AndroidRuntime(11004): Shutting down VM
08-23 16:11:05.413: W/dalvikvm(11004): threadid=1: thread exiting with uncaught exception (group=0x40015560)
08-23 16:11:05.423: E/AndroidRuntime(11004): FATAL EXCEPTION: main
08-23 16:11:05.423: E/AndroidRuntime(11004): java.lang.RuntimeException: Unable to start activity ComponentInfo{org.tomdroid/org.tomdroid.ui.Tomdroid}: java.lang.NullPointerException
08-23 16:11:05.423: E/AndroidRuntime(11004): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1647)
08-23 16:11:05.423: E/AndroidRuntime(11004): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1663)
08-23 16:11:05.423: E/AndroidRuntime(11004): at android.app.ActivityThread.access$1500(ActivityThread.java:117)
08-23 16:11:05.423: E/AndroidRuntime(11004): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:931)
08-23 16:11:05.423: E/AndroidRuntime(11004): at android.os.Handler.dispatchMessage(Handler.java:99)
08-23 16:11:05.423: E/AndroidRuntime(11004): at android.os.Looper.loop(Looper.java:130)
08-23 16:11:05.423: E/AndroidRuntime(11004): at android.app.ActivityThread.main(ActivityThread.java:3683)
08-23 16:11:05.423: E/AndroidRuntime(11004): at java.lang.reflect.Method.invokeNative(Native Method)
08-23 16:11:05.423: E/AndroidRuntime(11004): at java.lang.reflect.Method.invoke(Method.java:507)
08-23 16:11:05.423: E/AndroidRuntime(11004): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:839)
08-23 16:11:05.423: E/AndroidRuntime(11004): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
08-23 16:11:05.423: E/AndroidRuntime(11004): at dalvik.system.NativeStart.main(Native Method)
08-23 16:11:05.423: E/AndroidRuntime(11004): Caused by: java.lang.NullPointerException
08-23 16:11:05.423: E/AndroidRuntime(11004): at org.tomdroid.sync.SyncService.getDescription(SyncService.java:132)
08-23 16:11:05.423: E/AndroidRuntime(11004): at org.tomdroid.ui.Tomdroid.onCreateDialog(Tomdroid.java:604)
08-23 16:11:05.423: E/AndroidRuntime(11004): at android.app.Activity.onCreateDialog(Activity.java:2482)
08-23 16:11:05.423: E/AndroidRuntime(11004): at android.app.Activity.createDialog(Activity.java:882)
08-23 16:11:05.423: E/AndroidRuntime(11004): at android.app.Activity.restoreManagedDialogs(Activity.java:871)
08-23 16:...

Read more...

Changed in tomdroid:
status: New → Triaged
importance: Undecided → High
milestone: none → 0.7.2
Revision history for this message
NoahY (noahy) wrote :

Can someone get a stacktrace with the latest revision? It may be fixed now, but that line number is invalid and I can't see what it is referring to.

Changed in tomdroid:
status: Triaged → Incomplete
Revision history for this message
Stefan Hammer (j-4-deactivatedaccount) wrote :

I still have crashes, but whenever I get one, I am not connected to the computer.
I now installed aLogcat to grep the stacktrace!

Revision history for this message
NoahY (noahy) wrote :

Me too, thanks for the tip - I'll install the app and try to get a logcat as well.

Revision history for this message
Stefan Hammer (j-4-deactivatedaccount) wrote :
Download full text (4.7 KiB)

I just got a crash. Didn't use tomdroid for a while, than started and directly crashed. When starting right afterwards it worked again.

I/ActivityManager( 140): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=org.tomdroid/.ui.Tomdroid bnds=[245,231][355,349] } from pid 227
I/ActivityManager( 140): Start proc org.tomdroid for activity org.tomdroid/.ui.Tomdroid: pid=15928 uid=10047 gids={3003, 1015}
I/ActivityThread(15928): Pub org.tomdroid.notes: org.tomdroid.NoteProvider
I/ActivityThread(15928): Pub org.tomdroid.util.SearchSuggestionProvider: org.tomdroid.util.SearchSuggestionProvider
V/RenderScript_jni( 227): surfaceDestroyed
D/AndroidRuntime(15928): Shutting down VM
W/dalvikvm(15928): threadid=1: thread exiting with uncaught exception (group=0x40015560)
E/AndroidRuntime(15928): FATAL EXCEPTION: main
E/AndroidRuntime(15928): java.lang.RuntimeException: Unable to start activity ComponentInfo{org.tomdroid/org.tomdroid.ui.Tomdroid}: java.lang.NullPointerException
E/AndroidRuntime(15928): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1647)
E/AndroidRuntime(15928): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1663)
E/AndroidRuntime(15928): at android.app.ActivityThread.access$1500(ActivityThread.java:117)
E/AndroidRuntime(15928): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:931)
E/AndroidRuntime(15928): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(15928): at android.os.Looper.loop(Looper.java:130)
E/AndroidRuntime(15928): at android.app.ActivityThread.main(ActivityThread.java:3683)
E/AndroidRuntime(15928): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(15928): at java.lang.reflect.Method.invoke(Method.java:507)
E/AndroidRuntime(15928): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:839)
E/AndroidRuntime(15928): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
E/AndroidRuntime(15928): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime(15928): Caused by: java.lang.NullPointerException
E/AndroidRuntime(15928): at org.tomdroid.sync.SyncService.getDescription(SyncService.java:133)
E/AndroidRuntime(15928): at org.tomdroid.ui.Tomdroid.onCreateDialog(Tomdroid.java:625)
E/AndroidRuntime(15928): at android.app.Activity.onCreateDialog(Activity.java:2482)
E/AndroidRuntime(15928): at android.app.Activity.createDialog(Activity.java:882)
E/AndroidRuntime(15928): at android.app.Activity.restoreManagedDialogs(Activity.java:871)
E/AndroidRuntime(15928): at android.app.Activity.performRestoreInstanceState(Activity.java:817)
E/AndroidRuntime(15928): at android.app.Instrumentation.callActivityOnRestoreInstanceState(Instrumentation.java:1096)
E/AndroidRuntime(15928): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1625)
E/AndroidRuntime(15928): ... 11 more
W/ActivityManager( 140): Force finishing activity org.tomdroid/.ui.Tomdroid
W/ActivityManager( 140): Activity pause timeout for HistoryRecord{4081b9b8 org.tomdroid/.ui.Tomdroid}
V/RenderScript_jni( 227): surfaceCreated
V...

Read more...

Revision history for this message
Stefan Hammer (j-4-deactivatedaccount) wrote :

E/AndroidRuntime(15928): at org.tomdroid.sync.SyncService.getDescription(SyncService.java:133)

the sync service description is passed as a integer from the sync service and then read from string.xml in the preferences dialouge.

maybe there is the problem somehow. you also read the sync service for the syncing dialouge. maybe preferences are not initialized or something... we have to figure this out somehow - it is always the same exception for all this random crashes at the moment.

Revision history for this message
NoahY (noahy) wrote :

Now that I look at the stack traces again, I see what the problem is - it is actually two different instances of the same problem, not passing the activity to SyncService in both onCreate and onResume. If I am not mistaken, these are both fixed in the latest revision - Stefan, which revision are you getting the fc on?

Revision history for this message
Stefan Hammer (j-4-deactivatedaccount) wrote :

i have 435 atm. your latest fixes from today are not included.
Thanks for having a closer look at this! I will confirm if it is fixed in the evening!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.