[TIMOB-14947] Android: WebView crashes on Android 2.3.3 Emulator
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Critical |
Status | Closed |
Resolution | Not Our Bug |
Resolution Date | 2013-10-08T21:40:09.000+0000 |
Affected Version/s | n/a |
Fix Version/s | n/a |
Components | Android |
Labels | android, defect, emulator, regression, titanbeta |
Reporter | Shawn Lipscomb |
Assignee | Ingo Muschenetz |
Created | 2013-08-23T21:04:59.000+0000 |
Updated | 2017-03-29T20:56:41.000+0000 |
Description
*Problem*
Trying to display a simple WebView crashes on Android 2.3.3. The specific webpage is not important...I have included one in the testcase below that is very simple. The page displays for a brief moment, and then the app completely crashes and closes.
*Test case*
var win1 = Ti.UI.createWindow({
layout : 'vertical'
});
var WebView = Ti.UI.createWebView({
url : 'http://www.york.ac.uk/teaching/cws/wws/webpage1.html'
});
win1.add(WebView);
win1.open();
*Crash Log*
[WARN][dalvikvm( 453)] JNI WARNING: jarray 0x4051e900 points to non-array object (Ljava/lang/String;)
[INFO][dalvikvm( 453)] "WebViewCoreThread" prio=5 tid=13 NATIVE
[INFO][dalvikvm( 453)] | group="main" sCount=0 dsCount=0 obj=0x40510d98 self=0x20e4f0
[INFO][dalvikvm( 453)] | sysTid=468 nice=0 sched=0/0 cgrp=default handle=2156072
[INFO][dalvikvm( 453)] | schedstat=( 332645819 649272130 82 )
[INFO][dalvikvm( 453)] at android.webkit.JWebCoreJavaBridge.sharedTimerFired(Native Method)
[INFO][dalvikvm( 453)] at android.webkit.JWebCoreJavaBridge.sharedTimerFired(Native Method)
[INFO][dalvikvm( 453)] at android.webkit.JWebCoreJavaBridge.fireSharedTimer(JWebCoreJavaBridge.java:91)
[INFO][dalvikvm( 453)] at android.webkit.JWebCoreJavaBridge.handleMessage(JWebCoreJavaBridge.java:108)
[INFO][dalvikvm( 453)] at android.os.Handler.dispatchMessage(Handler.java:99)
[INFO][dalvikvm( 453)] at android.os.Looper.loop(Looper.java:123)
[INFO][dalvikvm( 453)] at android.webkit.WebViewCore$WebCoreThread.run(WebViewCore.java:629)
[INFO][dalvikvm( 453)] at java.lang.Thread.run(Thread.java:1019)
[INFO][dalvikvm( 453)]
[ERROR][dalvikvm( 453)] VM aborting
[INFO][DEBUG ( 31)] *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
[INFO][DEBUG ( 31)] Build fingerprint: 'generic/sdk/generic:2.3.3/GRI34/101070:eng/test-keys'
[INFO][DEBUG ( 31)] pid: 453, tid: 468 >>> com.eCotton.WebViewTest <<<
[INFO][DEBUG ( 31)] signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadd00d
[INFO][DEBUG ( 31)] r0 fffffec4 r1 deadd00d r2 00000026 r3 00000000
[INFO][DEBUG ( 31)] r4 800a45c0 r5 4051e900 r6 80085acc r7 0020e6f0
[INFO][DEBUG ( 31)] r8 45fffb58 r9 45d57f1c 10 45d57f04 fp 437cd8a0
[INFO][DEBUG ( 31)] ip 800a4720 sp 45fff678 lr afd19375 pc 80045a4a cpsr 20000030
[INFO][DEBUG ( 31)] #00 pc 00045a4a /system/lib/libdvm.so
[INFO][DEBUG ( 31)] #01 pc 00037748 /system/lib/libdvm.so
[INFO][DEBUG ( 31)] #02 pc 00039a10 /system/lib/libdvm.so
[INFO][DEBUG ( 31)] #03 pc 0003a4ec /system/lib/libdvm.so
[INFO][DEBUG ( 31)] #04 pc 002989d6 /system/lib/libwebcore.so
[INFO][DEBUG ( 31)] #05 pc 002120a4 /system/lib/libwebcore.so
[INFO][DEBUG ( 31)] #06 pc 00113216 /system/lib/libwebcore.so
[INFO][DEBUG ( 31)] #07 pc 00212b70 /system/lib/libwebcore.so
[INFO][DEBUG ( 31)] #08 pc 002c716e /system/lib/libwebcore.so
[INFO][DEBUG ( 31)] #09 pc 002ca4c6 /system/lib/libwebcore.so
[INFO][DEBUG ( 31)] #10 pc 002d83b0 /system/lib/libwebcore.so
[INFO][DEBUG ( 31)] #11 pc 002cfae8 /system/lib/libwebcore.so
[INFO][DEBUG ( 31)] #12 pc 00210094 /system/lib/libwebcore.so
[INFO][DEBUG ( 31)] #13 pc 00210112 /system/lib/libwebcore.so
[INFO][DEBUG ( 31)] #14 pc 00210180 /system/lib/libwebcore.so
[INFO][DEBUG ( 31)] #15 pc 001e7cc6 /system/lib/libwebcore.so
[INFO][DEBUG ( 31)] #16 pc 0007eeda /system/lib/libwebcore.so
[INFO][DEBUG ( 31)] #17 pc 0007ef84 /system/lib/libwebcore.so
[INFO][DEBUG ( 31)] #18 pc 0011b076 /system/lib/libwebcore.so
[INFO][DEBUG ( 31)] #19 pc 00017d74 /system/lib/libdvm.so
[INFO][DEBUG ( 31)] #20 pc 00048f08 /system/lib/libdvm.so
[INFO][DEBUG ( 31)] #21 pc 00041ab6 /system/lib/libdvm.so
[INFO][DEBUG ( 31)] #22 pc 0001cfd4 /system/lib/libdvm.so
[INFO][DEBUG ( 31)] #23 pc 000220dc /system/lib/libdvm.so
[INFO][DEBUG ( 31)] #24 pc 00020fd0 /system/lib/libdvm.so
[INFO][DEBUG ( 31)] #25 pc 0005f430 /system/lib/libdvm.so
[INFO][DEBUG ( 31)] #26 pc 0005f656 /system/lib/libdvm.so
[INFO][DEBUG ( 31)] #27 pc 00053b4e /system/lib/libdvm.so
[INFO][DEBUG ( 31)] #28 pc 00011a7c /system/lib/libc.so
[INFO][DEBUG ( 31)] #29 pc 00011640 /system/lib/libc.so
[INFO][DEBUG ( 31)]
[INFO][DEBUG ( 31)] code around pc:
[INFO][DEBUG ( 31)] 80045a28 447a4479 ed0cf7d1 20004c09 ee34f7d1
[INFO][DEBUG ( 31)] 80045a38 447c4808 6bdb5823 d0002b00 49064798
[INFO][DEBUG ( 31)] 80045a48 700a2226 eea0f7d1 000436b7 00045275
[INFO][DEBUG ( 31)] 80045a58 0005eb82 fffffec4 deadd00d b510b40e
[INFO][DEBUG ( 31)] 80045a68 4c0a4b09 447bb083 aa05591b 6b5bca02
[INFO][DEBUG ( 31)]
[INFO][DEBUG ( 31)] code around lr:
[INFO][DEBUG ( 31)] afd19354 b0834a0d 589c447b 26009001 686768a5
[INFO][DEBUG ( 31)] afd19364 220ce008 2b005eab 1c28d003 47889901
[INFO][DEBUG ( 31)] afd19374 35544306 d5f43f01 2c006824 b003d1ee
[INFO][DEBUG ( 31)] afd19384 bdf01c30 000281a8 ffffff88 1c0fb5f0
[INFO][DEBUG ( 31)] afd19394 43551c3d a904b087 1c16ac01 604d9004
[INFO][DEBUG ( 31)]
[INFO][DEBUG ( 31)] stack:
[INFO][DEBUG ( 31)] 45fff638 00000015
[INFO][DEBUG ( 31)] 45fff63c afd18407 /system/lib/libc.so
[INFO][DEBUG ( 31)] 45fff640 afd4270c /system/lib/libc.so
[INFO][DEBUG ( 31)] 45fff644 afd426b8 /system/lib/libc.so
[INFO][DEBUG ( 31)] 45fff648 00000000
[INFO][DEBUG ( 31)] 45fff64c afd19375 /system/lib/libc.so
[INFO][DEBUG ( 31)] 45fff650 0020e4f0 [heap]
[INFO][DEBUG ( 31)] 45fff654 afd183d9 /system/lib/libc.so
[INFO][DEBUG ( 31)] 45fff658 0020e6f0 [heap]
[INFO][DEBUG ( 31)] 45fff65c 0005eb82 [heap]
[INFO][DEBUG ( 31)] 45fff660 4051e900 /dev/ashmem/dalvik-heap (deleted)
[INFO][DEBUG ( 31)] 45fff664 80085acc /system/lib/libdvm.so
[INFO][DEBUG ( 31)] 45fff668 0020e6f0 [heap]
[INFO][DEBUG ( 31)] 45fff66c afd18437 /system/lib/libc.so
[INFO][DEBUG ( 31)] 45fff670 df002777
[INFO][DEBUG ( 31)] 45fff674 e3a070ad
[INFO][DEBUG ( 31)] #00 45fff678 00000001
[INFO][DEBUG ( 31)] 45fff67c 8003774d /system/lib/libdvm.so
[INFO][DEBUG ( 31)] #01 45fff680 00000001
[INFO][DEBUG ( 31)] 45fff684 80039a15 /system/lib/libdvm.so
[INFO][ActivityManager( 71)] Process com.eCotton.WebViewTest (pid 453) has died.
[ERROR][InputDispatcher( 71)] channel '409a58e8 com.eCotton.WebViewTest/com.eCotton.WebViewTest.WebviewtestActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x8
[ERROR][InputDispatcher( 71)] channel '409a58e8 com.eCotton.WebViewTest/com.eCotton.WebViewTest.WebviewtestActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
[INFO][WindowManager( 71)] WIN DEATH: Window{409a58e8 com.eCotton.WebViewTest/com.eCotton.WebViewTest.WebviewtestActivity paused=false}
[WARN][InputManagerService( 71)] Got RemoteException sending setActive(false) notification to pid 453 uid 10034
Tested on Android Emulator 2.3.3, with 2.1.4, 3.0.0, 3.1.2, crash occured in all. Tested with other Android versions no crash occurred.
Appears to be duplicates of the linked issues. We can see if there is any way to improve the situation.
On an Android 2.3.4 device (HTC), the WebView doesn't crash, but I get a "Web page not available" error. The web page displays fine on the 2.3.6 and 2.3.7 devices I tested with.
This is not our bug, and unfortunately any solution we can come to is a hack. However, this will be mitigated in large part by the fix for TIMOB-13983 where we won't default to the 2.3.3 android emulator by default, so users won't run into the issue nearly so often. From a duplicate of this issue: The 2.3 emulator has a known defect that means we can't use our Java <-> JS bridge (meaning any KS WebView tests will fail in the emulator). I tested this on my Nexus S and it looks fine, for any WebView tests we'll just have to use device only for now until Google gives us a fixed emulator. Android 2.3 Emulator / WebView bug: http://code.google.com/p/android/issues/detail?id=12987
Closing ticket as it has been established that the issue is not our bug.