Skip to first unread message
Alex Smith
Oct 12, 2014, 11:59:04 PM10/12/14
to andro...@googlegroups.com
I have an application permanently crashing on android-x86. It works fine on a tablet and a phone.
Is there a way to capture a crash state of the app. I believe it is related to android-x86. Therefore that could be helpful for devs and make android-x86 more stable.
Ralf ranfyy
Oct 13, 2014, 3:44:23 AM10/13/14
to andro...@googlegroups.com
Am Montag, 13. Oktober 2014 05:59:04 UTC+2 schrieb Alex Smith:
I have an application permanently crashing on android-x86. It works fine on a tablet and a phone.Is there a way to capture a crash state of the app. I believe it is related to android-x86. Therefore that could be helpful for devs and make android-x86 more stable.
In
Settings > Developer options
is there "take bug report" in android-x86 available (can't check it ATM)?
Other than that use the Android SDK for remote debugging.
Antony Stone
Oct 13, 2014, 3:51:45 AM10/13/14
to andro...@googlegroups.com
On Monday 13 October 2014 at 09:44:23 (EU time), Ralf ranfyy wrote:
> Am Montag, 13. Oktober 2014 05:59:04 UTC+2 schrieb Alex Smith:
>
> > I have an application permanently crashing on android-x86. It works fine
> > on a tablet and a phone.
> >
> > Is there a way to capture a crash state of the app. I believe it is
> > related to android-x86. Therefore that could be helpful for devs and make
> > android-x86 more stable.
>
> In
> Settings > Developer options
> is there "take bug report" in android-x86 available (can't check it ATM)?
Yes, that is present.
> Am Montag, 13. Oktober 2014 05:59:04 UTC+2 schrieb Alex Smith:
>
> > I have an application permanently crashing on android-x86. It works fine
> > on a tablet and a phone.
> >
> > Is there a way to capture a crash state of the app. I believe it is
> > related to android-x86. Therefore that could be helpful for devs and make
> > android-x86 more stable.
>
> In
> Settings > Developer options
> is there "take bug report" in android-x86 available (can't check it ATM)?
Antony.
--
Ramdisk is not an installation procedure.
Please reply to the list;
please *don't* CC me.
Ralf ranfyy
Oct 13, 2014, 3:58:45 AM10/13/14
to andro...@googlegroups.com, antony...@android.open.source.it
Am Montag, 13. Oktober 2014 09:51:45 UTC+2 schrieb Antony Stone:
On Monday 13 October 2014 at 09:44:23 (EU time), Ralf ranfyy wrote:
> Am Montag, 13. Oktober 2014 05:59:04 UTC+2 schrieb Alex Smith:
>
> > I have an application permanently crashing on android-x86. It works fine
> > on a tablet and a phone.
> >
> > Is there a way to capture a crash state of the app. I believe it is
> > related to android-x86. Therefore that could be helpful for devs and make
> > android-x86 more stable.
>
> In
> Settings > Developer options
> is there "take bug report" in android-x86 available (can't check it ATM)?
Yes, that is present.
Great.
This collects a lot of system info and sends it per mail to whoever you want.
Send this to yourself and read with a normal text editor or use this
Alex Smith
Oct 13, 2014, 6:24:00 PM10/13/14
to andro...@googlegroups.com
from the crash log:
app crashed:
...android.database.CursorWindowAllocationException,Cursor window allocation of 2048 kb failed. # Open Cursors=8 (# cursors opened by this proc=8),CursorWindow.java,104
Alex Smith
Oct 13, 2014, 11:09:03 PM10/13/14
to andro...@googlegroups.com
This is a full log section:
*** data_app_crash ***
Process: com.nubee.valkyriecrusade
Flags: 0x88be44
Package: com.nubee.valkyriecrusade v48 (2.5.0)
Build: Android-x86/android_x86/x86:4.4.2/KVT49L/eng.cwhuang.20140808.182504:userdebug/test-keys
android.database.CursorWindowAllocationException: Cursor window allocation of 2048 kb failed. # Open Cursors=8 (# cursors opened by this proc=8)
at android.database.CursorWindow.<init>(CursorWindow.java:104)
at android.database.AbstractWindowedCursor.clearOrCreateWindow(AbstractWindowedCursor.java:198)
at android.database.sqlite.SQLiteCursor.fillWindow(SQLiteCursor.java:139)
at android.database.sqlite.SQLiteCursor.getCount(SQLiteCursor.java:133)
at android.database.AbstractCursor.moveToPosition(AbstractCursor.java:197)
at android.database.AbstractCursor.moveToFirst(AbstractCursor.java:237)
at com.nubee.platform.notification.NotificationDBHelper.findFirst(NotificationDBHelper.java:75)
at com.nubee.platform.notification.LocalNotification.start(LocalNotification.java:37)
at com.nubee.platform.NubeePlatform.addLocalNotification(NubeePlatform.java:265)
at com.nubee.valkyriecrusade.GameRenderer.GlueOnPause(Native Method)
at com.nubee.valkyriecrusade.BaseActivity$1.run(BaseActivity.java:294)
at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1463)
at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1240)
*** data_app_native_crash ***
Process: com.nubee.valkyriecrusade
Flags: 0x88be44
Package: com.nubee.valkyriecrusade v48 (2.5.0)
Build: Android-x86/android_x86/x86:4.4.2/KVT49L/eng.cwhuang.20140808.182504:userdebug/test-keys
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'Android-x86/android_x86/x86:4.4.2/KVT49L/eng.cwhuang.20140808.182504:userdebug/test-keys'
Revision: '0'
pid: 26017, tid: 26035, name: Thread-243 >>> com.nubee.valkyriecrusade <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr dead0000
eax 00000000 ebx 7a65f640 ecx 79d1b854 edx 00000000
esi 00001000 edi 1c0045c0
xcs 00000073 xds 0000007b xes 0000007b xfs 00000043 xss 0000007b
eip 79b54393 ebp 7a65f658 esp 7a65f630 flags 00210246
backtrace:
#00 pc 0017a393 /system/lib/arm/libhoudini.so
#01 pc 000f7d86 /system/lib/arm/libhoudini.so
#02 pc 002148e7 /system/lib/arm/libhoudini.so
On Sunday, October 12, 2014 8:59:04 PM UTC-7, Alex Smith wrote:
Reply all
Reply to author
Forward
0 new messages