ExitApplication issue

KashMalaga · Oct 20, 2011

After use a webview component and use a Exit on a HorizontalScrollView, the app its crashing, the best part is if i use debugger doesnt found nothing, but debugger get crash too on ExitApplication line :sign0163:

I hope that Agraham or Erel can help me, i would like to fix it on private. Dont have problem on sending private the app.

Regards

Erel · Oct 20, 2011

Please check the unfiltered logs. There should be an error message there.

KashMalaga · Oct 20, 2011

Erel said:
Please check the unfiltered logs. There should be an error message there.

B4X:

I/DEBUG   ( 1023): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG   ( 1023): Build fingerprint: 'lge/lge_star/p990/p990:2.3.7/FRG83G/lgp990-V20j.2ED2ADCFFC:user/release-keys'
I/DEBUG   ( 1023): pid: 5121, tid: 5121  >>> com.xxxxxxx.test <<<
I/DEBUG   ( 1023): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 815a0a90
I/DEBUG   ( 1023):  r0 817ace04  r1 815a0a91  r2 00000001  r3 bec6c0d4
I/DEBUG   ( 1023):  r4 afd42504  r5 40008000  r6 40008954  r7 000000c5
I/DEBUG   ( 1023):  r8 00001000  r9 00000000  10 817ace04  fp 0000000c
I/DEBUG   ( 1023):  ip afd47450  sp bec6c0c8  lr afd1d175  pc 815a0a90  cpsr 68000030
I/DEBUG   ( 1023):  d0  403e00000000001e  d1  414ccccec3be0000
I/DEBUG   ( 1023):  d2  3e0888893e4cccce  d3  4436800043e50000
I/DEBUG   ( 1023):  d4  0000000000000000  d5  8000000000000000
I/DEBUG   ( 1023):  d6  43e58000c3be0000  d7  403e000000000000
I/DEBUG   ( 1023):  d8  c3be000042a00000  d9  0000000042a00000
I/DEBUG   ( 1023):  d10 0000000000000000  d11 0000000000000000
I/DEBUG   ( 1023):  d12 0000000000000000  d13 0000000000000000
I/DEBUG   ( 1023):  d14 0000000000000000  d15 0000000000000000
I/DEBUG   ( 1023):  scr 20000012
I/DEBUG   ( 1023): 
D/dalvikvm( 2050): GC_EXPLICIT freed 3K, 48% free 3103K/5895K, external 0K/0K, paused 66ms
D/dalvikvm( 4236): GC_EXPLICIT freed 8K, 49% free 2927K/5639K, external 0K/0K, paused 66ms

Logcat log when ExitApplication is on execution

:sign0085:

KashMalaga · Oct 21, 2011

Erel · Oct 21, 2011

I don't see any error in the reports. There should be a stack trace or something that gives more information on the error.

KashMalaga · Oct 26, 2011

Erel said:
I don't see any error in the reports. There should be a stack trace or something that gives more information on the error.

More info:

B4X:

10-26 19:50:42.269: I/InputDispatcher(1112): Application is not responding: Window{40748848 com.test/com.test.main paused=false}.  5007.6ms since event, 5007.4ms since wait started
10-26 19:50:42.269: I/WindowManager(1112): Input event dispatching timed out sending to com.test/com.test.main
10-26 19:50:42.320: I/Process(1112): Sending signal. PID: 21074 SIG: 3
10-26 19:50:42.320: I/dalvikvm(21074): threadid=4: reacting to signal 3
10-26 19:50:42.378: I/dalvikvm(21074): Wrote stack traces to '/data/anr/traces.txt'
10-26 19:50:42.378: I/Process(1112): Sending signal. PID: 1112 SIG: 3
10-26 19:50:42.378: I/dalvikvm(1112): threadid=4: reacting to signal 3
10-26 19:50:42.468: I/dalvikvm(1112): Wrote stack traces to '/data/anr/traces.txt'
10-26 19:50:42.468: I/Process(1112): Sending signal. PID: 1294 SIG: 3
10-26 19:50:42.468: I/dalvikvm(1294): threadid=4: reacting to signal 3
10-26 19:50:42.528: I/dalvikvm(1294): Wrote stack traces to '/data/anr/traces.txt'
10-26 19:50:42.528: I/Process(1112): Sending signal. PID: 1237 SIG: 3
10-26 19:50:42.528: I/dalvikvm(1237): threadid=4: reacting to signal 3
10-26 19:50:42.528: I/dalvikvm(1237): Wrote stack traces to '/data/anr/traces.txt'
10-26 19:50:42.798: D/dalvikvm(1112): GC_CONCURRENT freed 1328K, 35% free 7910K/12167K, external 1754K/2266K, paused 3ms+5ms
10-26 19:50:42.858: D/dalvikvm(1112): GC_EXPLICIT freed 35K, 36% free 7875K/12167K, external 1754K/2266K, paused 62ms
10-26 19:50:43.428: E/ActivityManager(1112): ANR in com.test (com.test/.main)
10-26 19:50:43.428: E/ActivityManager(1112): Reason: keyDispatchingTimedOut
10-26 19:50:43.428: E/ActivityManager(1112): Load: 1.38 / 1.52 / 1.39
10-26 19:50:43.428: E/ActivityManager(1112): CPU usage from 12721ms to 0ms ago:
10-26 19:50:43.428: E/ActivityManager(1112):   15% 21074/com.test: 15% user + 0.8% kernel / faults: 304 minor
10-26 19:50:43.428: E/ActivityManager(1112):   1.4% 1112/system_server: 0.6% user + 0.8% kernel / faults: 20 minor
10-26 19:50:43.428: E/ActivityManager(1112):   0% 470/tegra_touch_thr: 0% user + 0% kernel
10-26 19:50:43.428: E/ActivityManager(1112):   0.1% 248/cpufreq-dvfsd: 0% user + 0.1% kernel
10-26 19:50:43.428: E/ActivityManager(1112):   0.1% 587/motion_accel_wq: 0% user + 0.1% kernel
10-26 19:50:43.428: E/ActivityManager(1112):   0% 9/events/0: 0% user + 0% kernel
10-26 19:50:43.428: E/ActivityManager(1112):   0% 209/kblockd/0: 0% user + 0% kernel
10-26 19:50:43.428: E/ActivityManager(1112):   0% 532/battery_workque: 0% user + 0% kernel
10-26 19:50:43.428: E/ActivityManager(1112):   0% 956/mmcqd: 0% user + 0% kernel
10-26 19:50:43.428: E/ActivityManager(1112):   0% 971/flush-179:0: 0% user + 0% kernel
10-26 19:50:43.428: E/ActivityManager(1112):   0% 1032/nvrm_daemon: 0% user + 0% kernel
10-26 19:50:43.428: E/ActivityManager(1112):   0% 1087/adbd: 0% user + 0% kernel
10-26 19:50:43.428: E/ActivityManager(1112):   0% 18820/com.google.android.apps.maps:LocationFriendService: 0% user + 0% kernel / faults: 22 minor
10-26 19:50:43.428: E/ActivityManager(1112):   0% 20983/logcat: 0% user + 0% kernel / faults: 29 minor
10-26 19:50:43.428: E/ActivityManager(1112): 8.4% TOTAL: 7.1% user + 1% kernel + 0% iowait + 0.1% irq + 0% softirq
10-26 19:50:43.428: E/ActivityManager(1112): CPU usage from 597ms to 1112ms later:
10-26 19:50:43.428: E/ActivityManager(1112):   5.6% 1112/system_server: 1.8% user + 3.7% kernel / faults: 2 minor
10-26 19:50:43.428: E/ActivityManager(1112):     5.6% 1203/InputDispatcher: 0% user + 5.6% kernel
10-26 19:50:43.428: E/ActivityManager(1112): 5.7% TOTAL: 1.9% user + 3.8% kernel
10-26 19:50:43.448: I/InputDispatcher(1112): Dropping event because the pointer is not down.
10-26 19:50:43.448: I/InputDispatcher(1112): Dropping event because the pointer is not down.
10-26 19:50:43.448: I/InputDispatcher(1112): Dropping event because the pointer is not down.
10-26 19:51:09.241: I/power(1112): *** set_screen_state 0
10-26 19:51:09.278: D/(1032): NVRM_DAEMON(1179): pm_notifier_thread: Got message

10-26 19:51:09.278: D/(1032): NVRM_DAEMON(1191): pm_notifier_thread: calling power_displays(false)

10-26 19:51:09.278: D/(1032):  --- 1 :  *sus_disp_mask = 0xffffffff ,on=0

10-26 19:51:09.288: D/(1032): [PL] hitachi_cpu480X800_SetBacklight intensity1 =0

10-26 19:51:09.288: D/(1032): [PL] NvOdmDispDevicePowerLevel_Suspend

10-26 19:51:09.288: D/(1032): [BKL] bl_2x_panel_BacklightRelease

10-26 19:51:09.288: D/(1032): [BL] Display_Off buf =0

10-26 19:51:09.288: D/(1032): 

10-26 19:51:09.308: D/(1032): NVRM_DAEMON(1194): pm_notifier_thread: returned from power_displays(false)

10-26 19:51:09.308: D/(1032): NVRM_DAEMON(1207): pm_notifier_thread: Message serviced

10-26 19:51:09.758: W/ActivityManager(1112): Activity pause timeout for HistoryRecord{40800308 com.test/.main}
10-26 19:51:14.768: D/dalvikvm(19711): GC_EXPLICIT freed 1K, 46% free 3616K/6663K, external 0K/0K, paused 69ms

KashMalaga · Oct 26, 2011

Traces file uploaded

KashMalaga · Oct 27, 2011

up
:sign0085:

KashMalaga · Oct 28, 2011

up
:sign0085:

thedesolatesoul · Oct 28, 2011

Your logs dont look like b4a debugger logs, they are logcats.

You can either post your project or get the logs from b4a IDE.

Are you running on the emulator or real device?
On the b4a IDE, on your right is a Logs tab, click on that to get the debugger logs as well.

Erel · Oct 28, 2011

According to the traces file, the main thread hangs during the native exit command. It is not possible to know why it happens.

It seems to be an issue with WebView and ExitApplication. Why is ExitApplication required?
You can try calling ExitApplication with a short timer.

KashMalaga · Oct 29, 2011

Erel said:
According to the traces file, the main thread hangs during the native exit command. It is not possible to know why it happens.

It seems to be an issue with WebView and ExitApplication. Why is ExitApplication required?
You can try calling ExitApplication with a short timer.

Hello Erel,

I´ve got more info about it. ANR keyDispatchingTimedOut

This is the error that appears, i tried to set a short timer but the problems isnt be solved

KashMalaga · Oct 29, 2011

Fixed using in this case Activity.finish instead Exitapp... :sign0161:

ExitApplication issue

KashMalaga

Member

Erel

B4X founder

KashMalaga

Member

KashMalaga

Member

Erel

B4X founder

KashMalaga

Member

KashMalaga

Member

Attachments

KashMalaga

Member

KashMalaga

Member

thedesolatesoul

Expert

Erel

B4X founder

KashMalaga

Member

KashMalaga

Member

ExitApplication issue

Member

B4X founder

Member

Member

B4X founder

Member

Member

Attachments

Member

Member

Expert

B4X founder

Member

Member

Privacy & Transparency

Privacy & Transparency