webview和html5交互点击崩溃的问题+解决办法
来源:互联网 发布:苹果手机淘宝发布宝贝 编辑:程序博客网 时间:2024/05/21 18:46
07-07 19:06:05.350: W/dalvikvm(3076): threadid=4: spin on suspend #4 threadid=14 (pcf=0)
07-07 19:06:05.350: I/dalvikvm(3076): "Signal Catcher" daemon prio=5 tid=4 RUNNABLE
07-07 19:06:05.350: I/dalvikvm(3076): | group="system" sCount=0 dsCount=0 obj=0x40517940 self=0xf58d0
07-07 19:06:05.350: I/dalvikvm(3076): | sysTid=3079 nice=0 sched=0/0 cgrp=[no-cpu-subsys] handle=1169736
07-07 19:06:05.350: I/dalvikvm(3076): | schedstat=( 6835933 18493655 53 )
07-07 19:06:05.350: I/dalvikvm(3076): at dalvik.system.NativeStart.run(Native Method)
07-07 19:06:05.350: I/dalvikvm(3076): [<c0296320>] save_stack_trace_tsk+0x0/0x90
07-07 19:06:05.350: I/dalvikvm(3076): [<c03b77f4>] proc_pid_stack+0xf8/0x144
07-07 19:06:05.350: I/dalvikvm(3076): [<c03b8b58>] proc_single_show+0x48/0x84
07-07 19:06:05.350: I/dalvikvm(3076): [<c038d184>] seq_read+0x26c/0x4e4
07-07 19:06:05.350: I/dalvikvm(3076): [<c0373d44>] vfs_read+0xa8/0x150
07-07 19:06:05.350: I/dalvikvm(3076): [<c0373e98>] sys_read+0x3c/0x68
07-07 19:06:05.350: I/dalvikvm(3076): [<c0292740>] ret_fast_syscall+0x0/0x30
07-07 19:06:05.350: I/dalvikvm(3076): [<ffffffff>] 0xffffffff
07-07 19:06:05.350: I/dalvikvm(3076): ------------------------------
07-07 19:06:05.350: I/dalvikvm(3076): "WebViewCoreThread" prio=5 tid=14 RUNNABLE
07-07 19:06:05.350: I/dalvikvm(3076): | group="main" sCount=1 dsCount=0 obj=0x40614e08 self=0x279380
07-07 19:06:05.350: I/dalvikvm(3076): | sysTid=3165 nice=0 sched=0/0 cgrp=[no-cpu-subsys] handle=2523264
07-07 19:06:05.350: I/dalvikvm(3076): | schedstat=( 1820617722 1454437251 4540 )
07-07 19:06:05.350: I/dalvikvm(3076): at android.webkit.WebViewCore.nativeTouchUp(Native Method)
07-07 19:06:05.350: I/dalvikvm(3076): at android.webkit.WebViewCore.nativeTouchUp(Native Method)
07-07 19:06:05.350: I/dalvikvm(3076): at android.webkit.WebViewCore.access$6500(WebViewCore.java:63)
07-07 19:06:05.350: I/dalvikvm(3076): at android.webkit.WebViewCore$EventHub$1.handleMessage(WebViewCore.java:1780)
07-07 19:06:05.350: I/dalvikvm(3076): at android.os.Handler.dispatchMessage(Handler.java:99)
07-07 19:06:05.350: I/dalvikvm(3076): at android.os.Looper.loop(Looper.java:130)
07-07 19:06:05.350: I/dalvikvm(3076): at android.webkit.WebViewCore$WebCoreThread.run(WebViewCore.java:750)
07-07 19:06:05.350: I/dalvikvm(3076): at java.lang.Thread.run(Thread.java:1019)
07-07 19:06:05.350: I/dalvikvm(3076): "Signal Catcher" daemon prio=5 tid=4 RUNNABLE
07-07 19:06:05.350: I/dalvikvm(3076): | group="system" sCount=0 dsCount=0 obj=0x40517940 self=0xf58d0
07-07 19:06:05.350: I/dalvikvm(3076): | sysTid=3079 nice=0 sched=0/0 cgrp=[no-cpu-subsys] handle=1169736
07-07 19:06:05.350: I/dalvikvm(3076): | schedstat=( 6835933 18493655 53 )
07-07 19:06:05.350: I/dalvikvm(3076): at dalvik.system.NativeStart.run(Native Method)
07-07 19:06:05.350: I/dalvikvm(3076): [<c0296320>] save_stack_trace_tsk+0x0/0x90
07-07 19:06:05.350: I/dalvikvm(3076): [<c03b77f4>] proc_pid_stack+0xf8/0x144
07-07 19:06:05.350: I/dalvikvm(3076): [<c03b8b58>] proc_single_show+0x48/0x84
07-07 19:06:05.350: I/dalvikvm(3076): [<c038d184>] seq_read+0x26c/0x4e4
07-07 19:06:05.350: I/dalvikvm(3076): [<c0373d44>] vfs_read+0xa8/0x150
07-07 19:06:05.350: I/dalvikvm(3076): [<c0373e98>] sys_read+0x3c/0x68
07-07 19:06:05.350: I/dalvikvm(3076): [<c0292740>] ret_fast_syscall+0x0/0x30
07-07 19:06:05.350: I/dalvikvm(3076): [<ffffffff>] 0xffffffff
07-07 19:06:05.350: I/dalvikvm(3076): ------------------------------
07-07 19:06:05.350: I/dalvikvm(3076): "WebViewCoreThread" prio=5 tid=14 RUNNABLE
07-07 19:06:05.350: I/dalvikvm(3076): | group="main" sCount=1 dsCount=0 obj=0x40614e08 self=0x279380
07-07 19:06:05.350: I/dalvikvm(3076): | sysTid=3165 nice=0 sched=0/0 cgrp=[no-cpu-subsys] handle=2523264
07-07 19:06:05.350: I/dalvikvm(3076): | schedstat=( 1820617722 1454437251 4540 )
07-07 19:06:05.350: I/dalvikvm(3076): at android.webkit.WebViewCore.nativeTouchUp(Native Method)
07-07 19:06:05.350: I/dalvikvm(3076): at android.webkit.WebViewCore.nativeTouchUp(Native Method)
07-07 19:06:05.350: I/dalvikvm(3076): at android.webkit.WebViewCore.access$6500(WebViewCore.java:63)
07-07 19:06:05.350: I/dalvikvm(3076): at android.webkit.WebViewCore$EventHub$1.handleMessage(WebViewCore.java:1780)
07-07 19:06:05.350: I/dalvikvm(3076): at android.os.Handler.dispatchMessage(Handler.java:99)
07-07 19:06:05.350: I/dalvikvm(3076): at android.os.Looper.loop(Looper.java:130)
07-07 19:06:05.350: I/dalvikvm(3076): at android.webkit.WebViewCore$WebCoreThread.run(WebViewCore.java:750)
07-07 19:06:05.350: I/dalvikvm(3076): at java.lang.Thread.run(Thread.java:1019)
07-07 19:06:05.350: I/dalvikvm(3076): [<ffffffff>] 0xffffffff
最近在做一个项目,涉及html5和native交互,交互过程中会出现上面的log。
前提:
1.一个activity有七屏,每一屏对应一个Fragment,每一个Fragment对应一个webview
2.每一个webview都执行了该方法
mWebView.addJavascriptInterface(new NativeHtml5(getActivity()), "js2java_android");
现象:
1.点击首页内容后,就出现闪退。log为以上。
解决办法:
1.一个activity只保持一个NativeHtml5 对象。即不要每一个Fragment就new 一个js接口。
- webview和html5交互点击崩溃的问题+解决办法
- Webview和Html5的交互
- WebView和html5 的交互
- Android app嵌套html5之Webview和js的交互
- Android app嵌套html5之Webview和js的交互
- iOS 与HTML5交互之捕捉HTML5按钮点击事件,获取webview上按钮的点击事件
- iOS 与HTML5交互之捕捉HTML5按钮点击事件,获取webview上按钮的点击事件
- iOS和html5交互遇到的问题
- 关于WebView.destroy()崩溃的解决办法
- WebView和ListView的交互使用,异步加载的问题
- webview和js的交互
- app和WebView的交互
- webview和js的交互
- webview和h5的交互
- Java 和webview 的交互
- WebView和Web的交互
- webView 和Js的交互
- js和webview的交互
- 引入外部实体1
- 子序列最大连续和(动态规划、分治)
- Eming
- xml内部实体的引用
- XML引入样式
- webview和html5交互点击崩溃的问题+解决办法
- WCF 项目应用连载[2] - 创建Lig日志系统
- poj1482 & hdu1818 It's not a Bug, It's a Feature!(bfs+状态压缩)
- xml 软件校验
- pppd 中文man页面
- 一个简单的智能指针实现
- c语言--内部名外部名
- pppd englist man
- 复选框设置开机启动与取消