bug: Webview crashes application in Emulator v.2.1 (core 1.18)

peacemaker

Expert
Licensed User
Longtime User
First LoadUrl is OK in Android 2.1, but next link click crashes the application (uninspectedly), v.1.6, 2.2 and 2.3 are OK:



HTML:
obtainBuffer timed out (is the CPU pegged?) 0x3e488 user=00002b89, server=000008b5


Displayed activity test.test/.main: 2531 ms (total 2531 ms)


obtainBuffer timed out (is the CPU pegged?) 0x3e488 user=00002b89, server=000008b5


obtainBuffer timed out (is the CPU pegged?) 0x3e488 user=00002b89, server=000008b5


obtainBuffer timed out (is the CPU pegged?) 0x9cac8 user=000022d4, server=00000000


obtainBuffer timed out (is the CPU pegged?) 0x6fb98 user=000022d4, server=00000000


obtainBuffer timed out (is the CPU pegged?) 0xbfc08 user=000022d4, server=00000000


finished2


obtainBuffer timed out (is the CPU pegged?) 0x3e488 user=00002b89, server=000008b5


obtainBuffer timed out (is the CPU pegged?) 0x3e488 user=00002b89, server=000008b5


obtainBuffer timed out (is the CPU pegged?) 0x9cac8 user=000022d4, server=00000000


obtainBuffer timed out (is the CPU pegged?) 0x6fb98 user=000022d4, server=00000000


obtainBuffer timed out (is the CPU pegged?) 0xbfc08 user=000022d4, server=00000000


obtainBuffer timed out (is the CPU pegged?) 0x3e488 user=00002b89, server=000008b5


obtainBuffer timed out (is the CPU pegged?) 0x3e488 user=00002b89, server=000008b5


GC freed 1222 objects / 62296 bytes in 496ms


GC freed 4671 objects / 339872 bytes in 109ms


threadid=15: thread exiting with uncaught exception (group=0x4001b188)


Uncaught handler: thread WebViewCoreThread exiting due to uncaught exception


java.lang.ArrayIndexOutOfBoundsException


   at android.webkit.MimeTypeMap.getSingleton(MimeTypeMap.java:442)


   at android.webkit.LoadListener.guessMimeTypeFromExtension(LoadListener.java:1456)


   at android.webkit.LoadListener.guessMimeType(LoadListener.java:1440)


   at android.webkit.LoadListener.handleHeaders(LoadListener.java:350)


   at android.webkit.LoadListener.handleMessage(LoadListener.java:176)


   at android.os.Handler.dispatchMessage(Handler.java:99)


   at android.os.Looper.loop(Looper.java:123)


   at android.webkit.WebViewCore$WebCoreThread.run(WebViewCore.java:611)


   at java.lang.Thread.run(Thread.java:1096)


Sending signal. PID: 798 SIG: 3


threadid=7: reacting to signal 3


Unable to open stack trace file '/data/anr/traces.txt': Permission denied


obtainBuffer timed out (is the CPU pegged?) 0x3e488 user=00002b89, server=000008b5


obtainBuffer timed out (is the CPU pegged?) 0x9cac8 user=000022d4, server=00000000


obtainBuffer timed out (is the CPU pegged?) 0x6fb98 user=000022d4, server=00000000


obtainBuffer timed out (is the CPU pegged?) 0xbfc08 user=000022d4, server=00000000


obtainBuffer timed out (is the CPU pegged?) 0x3e488 user=00002b89, server=000008b5


obtainBuffer timed out (is the CPU pegged?) 0x3e488 user=00002b89, server=000008b5


obtainBuffer timed out (is the CPU pegged?) 0x3e488 user=00002b89, server=000008b5


obtainBuffer timed out (is the CPU pegged?) 0x9cac8 user=000022d4, server=00000000


obtainBuffer timed out (is the CPU pegged?) 0x6fb98 user=000022d4, server=00000000


obtainBuffer timed out (is the CPU pegged?) 0xbfc08 user=000022d4, server=00000000


obtainBuffer timed out (is the CPU pegged?) 0x3e488 user=00002b89, server=000008b5


obtainBuffer timed out (is the CPU pegged?) 0x3e488 user=00002b89, server=000008b5


obtainBuffer timed out (is the CPU pegged?) 0x3e488 user=00002b89, server=000008b5

Update: more over starting browser also makes a crash in 2.1 :-(
HTML:
Sub btnGo_LongClick
   Dim p As PhoneIntents
   StartActivity (p.OpenBrowser(txtURL0.Text))
End Sub
 
Last edited:

agraham

Expert
Licensed User
Longtime User
If it is only in the emulator and not on a real device then I would not worry. It looks like some sort of timeout and Android 2.1 is probably the slowest version, 1.6 is a bit "lighter" and 2.2 and later have a Just In Time compiler which speeds things up.
 
Cookies are required to use this site. You must accept them to continue using the site. Learn more…