FC on startup..

A place to submit bugs to the Andor's Trail Development Team.
Post Reply
escargot
Posts: 11
Joined: Thu Apr 14, 2011 5:58 am

FC on startup..

Post by escargot »

if I try to open the game in the recent apps menu (via holding the home button), I get a force close every time. I haven't had any problems opening it from the app drawer & haven't tried from a desktop shortcut yet.

using version 2.2.1; LG ally.

not sure what other information is needed. let me know.
|LVL 17|XP 83370|HP 50|ATK $ 03|ATK % 114*|ATK DMG 17-22*|
|CRIT HIT % 10|CRIT HIT X 02|BLOCK % 45*|RESIST NA|UPD 04/17|

* BASE STATS = 85 (ATK %), 04 (ATK DMG) & 09 (BLOCK %)
. .. .@Y
sdevaney
Site Admin
Posts: 1178
Joined: Fri Jan 28, 2011 10:17 pm
android_version: 14 - Android 14
Contact:

Re: FC on startup..

Post by sdevaney »

Strange, I just tried on my Droid Incredible running 2.2 and I get no force close. I even went and killed the application manually and still no force close.

Can anyone else re-create this bug?
escargot
Posts: 11
Joined: Thu Apr 14, 2011 5:58 am

Re: FC on startup..

Post by escargot »

maybe it's a conflict with the launcher app I'm using? (adw). give me a sec & I'll test it without.

edit: hm. same issue when I'm not using the launcher...
|LVL 17|XP 83370|HP 50|ATK $ 03|ATK % 114*|ATK DMG 17-22*|
|CRIT HIT % 10|CRIT HIT X 02|BLOCK % 45*|RESIST NA|UPD 04/17|

* BASE STATS = 85 (ATK %), 04 (ATK DMG) & 09 (BLOCK %)
. .. .@Y
Fruit Fly
Posts: 15
Joined: Sat Mar 05, 2011 12:12 am

Re: FC on startup..

Post by Fruit Fly »

I just tried it, I had no problem opening it from the recent apps menu. Another positive... I now know I have a recent apps menu. I didn't know about that feature on my phone lol.
kabbie1882
Posts: 170
Joined: Thu Mar 24, 2011 5:38 am

Re: FC on startup..

Post by kabbie1882 »

Works fine soft and hard home button, on Nook Color CM7.0.0/Android2.3.3
Ha Ha, Made you look.
Johan
Posts: 46
Joined: Mon Apr 11, 2011 11:16 am
android_version: 5.1 - Lolipop
Location: Lurking several months behind

Re: FC on startup..

Post by Johan »

I have seen this behavior a few times as well and I think it happens when the app has been terminated by the OS because of memory shortage. I will see if I can capture some logs when it happens next time.
Johan
Posts: 46
Joined: Mon Apr 11, 2011 11:16 am
android_version: 5.1 - Lolipop
Location: Lurking several months behind

Re: FC on startup..

Post by Johan »

And here are the logs.

System log
05-01 13:19:13.441 I/WindowManager( 78): WIN DEATH: Window{44d9d280 com.gpl.rpg.AndorsTrail/com.gpl.rpg.AndorsTrail.activity.StartScreenActivity paused=false}
05-01 13:19:13.441 I/ActivityManager( 78): Process com.gpl.rpg.AndorsTrail (pid 3601) has died.
05-01 13:19:13.441 I/WindowManager( 78): WIN DEATH: Window{44ae9048 com.gpl.rpg.AndorsTrail/com.gpl.rpg.AndorsTrail.activity.MainActivity paused=false}
05-01 13:28:11.043 I/ActivityManager( 78): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10100000 cmp=com.gpl.rpg.AndorsTrail/.activity.StartScreenActivity }
05-01 13:28:11.153 I/ActivityManager( 78): Start proc com.gpl.rpg.AndorsTrail for activity com.gpl.rpg.AndorsTrail/.activity.MainActivity: pid=5297 uid=10048 gids={1015}
05-01 13:28:11.283 I/dalvikvm( 5297): Debugger thread not active, ignoring DDM send (t=0x41504e4d l=38)
05-01 13:28:11.403 I/dalvikvm( 5297): Debugger thread not active, ignoring DDM send (t=0x41504e4d l=50)
05-01 13:28:11.713 D/AndroidRuntime( 5297): Shutting down VM
05-01 13:28:11.713 W/dalvikvm( 5297): threadid=3: thread exiting with uncaught exception (group=0x4001e390)
05-01 13:28:11.713 E/AndroidRuntime( 5297): Uncaught handler: thread main exiting due to uncaught exception
05-01 13:28:11.763 E/AndroidRuntime( 5297): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.gpl.rpg.AndorsTrail/com.gpl.rpg.AndorsTrail.activity.MainActivity}: android.view.InflateException: Binary XML file line #8: Error inflating class com.gpl.rpg.AndorsTrail.view.StatusView
05-01 13:28:11.763 E/AndroidRuntime( 5297): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2596)
05-01 13:28:11.763 E/AndroidRuntime( 5297): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2621)
05-01 13:28:11.763 E/AndroidRuntime( 5297): at android.app.ActivityThread.access$2200(ActivityThread.java:126)
05-01 13:28:11.763 E/AndroidRuntime( 5297): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1932)
05-01 13:28:11.763 E/AndroidRuntime( 5297): at android.os.Handler.dispatchMessage(Handler.java:99)
05-01 13:28:11.763 E/AndroidRuntime( 5297): at android.os.Looper.loop(Looper.java:123)
05-01 13:28:11.763 E/AndroidRuntime( 5297): at android.app.ActivityThread.main(ActivityThread.java:4595)
05-01 13:28:11.763 E/AndroidRuntime( 5297): at java.lang.reflect.Method.invokeNative(Native Method)
05-01 13:28:11.763 E/AndroidRuntime( 5297): at java.lang.reflect.Method.invoke(Method.java:521)
05-01 13:28:11.763 E/AndroidRuntime( 5297): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
05-01 13:28:11.763 E/AndroidRuntime( 5297): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
05-01 13:28:11.763 E/AndroidRuntime( 5297): at dalvik.system.NativeStart.main(Native Method)
05-01 13:28:11.763 E/AndroidRuntime( 5297): Caused by: android.view.InflateException: Binary XML file line #8: Error inflating class com.gpl.rpg.AndorsTrail.view.StatusView
05-01 13:28:11.763 E/AndroidRuntime( 5297): at android.view.LayoutInflater.createView(LayoutInflater.java:513)
05-01 13:28:11.763 E/AndroidRuntime( 5297): at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:565)
05-01 13:28:11.763 E/AndroidRuntime( 5297): at android.view.LayoutInflater.rInflate(LayoutInflater.java:618)
05-01 13:28:11.763 E/AndroidRuntime( 5297): at android.view.LayoutInflater.inflate(LayoutInflater.java:407)
05-01 13:28:11.763 E/AndroidRuntime( 5297): at android.view.LayoutInflater.inflate(LayoutInflater.java:320)
05-01 13:28:11.763 E/AndroidRuntime( 5297): at android.view.LayoutInflater.inflate(LayoutInflater.java:276)
05-01 13:28:11.763 E/AndroidRuntime( 5297): at com.android.internal.policy.impl.PhoneWindow.setContentView(PhoneWindow.java:207)
05-01 13:28:11.763 E/AndroidRuntime( 5297): at android.app.Activity.setContentView(Activity.java:1629)
05-01 13:28:11.763 E/AndroidRuntime( 5297): at com.gpl.rpg.AndorsTrail.activity.MainActivity.onCreate(MainActivity.java:70)
05-01 13:28:11.763 E/AndroidRuntime( 5297): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
05-01 13:28:11.763 E/AndroidRuntime( 5297): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2544)
05-01 13:28:11.763 E/AndroidRuntime( 5297): ... 11 more
05-01 13:28:11.763 E/AndroidRuntime( 5297): Caused by: java.lang.reflect.InvocationTargetException
05-01 13:28:11.763 E/AndroidRuntime( 5297): at com.gpl.rpg.AndorsTrail.view.StatusView.<init>(StatusView.java:36)
05-01 13:28:11.763 E/AndroidRuntime( 5297): at java.lang.reflect.Constructor.constructNative(Native Method)
05-01 13:28:11.763 E/AndroidRuntime( 5297): at java.lang.reflect.Constructor.newInstance(Constructor.java:446)
05-01 13:28:11.763 E/AndroidRuntime( 5297): at android.view.LayoutInflater.createView(LayoutInflater.java:500)
05-01 13:28:11.763 E/AndroidRuntime( 5297): ... 21 more
05-01 13:28:11.763 E/AndroidRuntime( 5297): Caused by: java.lang.NullPointerException
05-01 13:28:11.763 E/AndroidRuntime( 5297): ... 25 more
05-01 13:28:11.823 I/Process ( 78): Sending signal. PID: 5297 SIG: 3
05-01 13:28:11.823 I/dalvikvm( 5297): threadid=7: reacting to signal 3
05-01 13:28:11.843 I/dalvikvm( 5297): Wrote stack trace to '/data/anr/traces.txt'
05-01 13:28:13.573 I/Process ( 5297): Sending signal. PID: 5297 SIG: 9
05-01 13:28:13.583 D/ActivityManager( 78): foreground app died, app = com.gpl.rpg.AndorsTrail
05-01 13:28:13.583 I/ActivityManager( 78): Process com.gpl.rpg.AndorsTrail (pid 5297) has died.
05-01 13:28:13.633 I/ActivityManager( 78): Start proc com.gpl.rpg.AndorsTrail for activity com.gpl.rpg.AndorsTrail/.activity.StartScreenActivity: pid=5302 uid=10048 gids={1015}
05-01 13:28:13.783 I/UsageStats( 78): Unexpected resume of com.gpl.rpg.AndorsTrail while already resumed in com.gpl.rpg.AndorsTrail
05-01 13:28:14.403 I/ActivityManager( 78): Displayed activity com.gpl.rpg.AndorsTrail/.activity.StartScreenActivity: 808 ms (total 3283 ms)
Stack trace
----- pid 5297 at 2011-05-01 13:28:11 -----
Cmd line: com.gpl.rpg.AndorsTrail

DALVIK THREADS:
"main" prio=5 tid=3 NATIVE
| group="main" sCount=1 dsCount=0 s=N obj=0x4001e470 self=0xbdd0
| sysTid=5297 nice=0 sched=0/0 cgrp=default handle=-1344001372
at android.os.BinderProxy.transact(Native Method)
at android.app.ActivityManagerProxy.handleApplicationError(ActivityManagerNative.java:2387)
at com.android.internal.os.RuntimeInit.crash(RuntimeInit.java:339)
at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:76)
at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:887)
at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:884)
at dalvik.system.NativeStart.main(Native Method)

"Binder Thread #2" prio=5 tid=11 NATIVE
| group="main" sCount=1 dsCount=0 s=N obj=0x4489eab8 self=0x16a000
| sysTid=5301 nice=0 sched=0/0 cgrp=default handle=1497248
at dalvik.system.NativeStart.run(Native Method)

"Binder Thread #1" prio=5 tid=9 NATIVE
| group="main" sCount=1 dsCount=0 s=N obj=0x4489a280 self=0x16a8b0
| sysTid=5300 nice=0 sched=0/0 cgrp=default handle=1493640
at dalvik.system.NativeStart.run(Native Method)

"Signal Catcher" daemon prio=5 tid=7 RUNNABLE
| group="system" sCount=0 dsCount=0 s=N obj=0x448981e8 self=0x1763d0
| sysTid=5299 nice=0 sched=0/0 cgrp=default handle=1516680
at dalvik.system.NativeStart.run(Native Method)

"HeapWorker" daemon prio=5 tid=5 VMWAIT
| group="system" sCount=1 dsCount=0 s=N obj=0x43b4b718 self=0x16a680
| sysTid=5298 nice=0 sched=0/0 cgrp=default handle=1382568
at dalvik.system.NativeStart.run(Native Method)

----- end 5297 -----
oskarwiksten
Captain Awesome
Posts: 368
Joined: Sat Jan 29, 2011 8:51 am
android_version: 2.3 - Gingerbread
Location: Stockholm, Sweden

Re: FC on startup..

Post by oskarwiksten »

Thanks for the stacktrace Johan.

It might have something to do with memory shortage, which *might* be solved by the next update. Because of the massive amounts of new maps for the new version, the map loading is re-wired to only load the maps that the player is on. This might solve it.

But then again, it might be something totally different that causes it :)
/Oskar
Post Reply