Hello World App在Cordova 6.4.0中崩溃

Question

我是Cordova的新手,我无法将Cordova"hello world"应用程序显示在Android Emulator上,但我可以在浏览器中成功运行相同的应用程序.此外,我可以在在线云模拟器中运行该应用程序.

Cordova版本:6.4.0

NodeJs:4.6.1

Ubuntu:14.04 64位

这是我的android虚拟设备设置

这是我尝试运行hello world应用程序时的堆栈跟踪.

[11-08 08:45:27.115 3256:3256 W/google-breakpad]

### ### ### ### ### ### ### ### ### ### ###

[11-08 08:45:27.115 3256:3256 W/google-breakpad] Chrome构建指纹:

[11-08 08:45:27.115 3256:3256 W/google-breakpad] 1.0.0

[11-08 08:45:27.115 3256:3256 W/google-breakpad] 10000

[11-08 08:45:27.115 3256:3256 W/google-breakpad] 3874b69a-4a70-400e-94db-0744eafe8cbf

[11-08 08:45:27.115 3256:3256 W/google-breakpad]

### ### ### ### ### ### ### ### ### ### ###

[11-08 08:45:27.115 3256:3256 F/libc]致命信号6(SIGABRT),tid 3256中的代码-6(m.example.hello)

[11-08 08:45:27.115 1183:1183 W /] debuggerd:处理请求:pid = 3256 uid = 10060 gid = 10060 tid = 3256

[11-08 08:45:27.119 3275:3275 F/DEBUG]

---

[11-08 08:45:27.119 3275:3275 F/DEBUG]构建指纹:'Android/sdk_phone_x86_64/generic_x86_64:7.0/NYC/3245079:userdebug/test-keys'

[11-08 08:45:27.119 3275:3275 F/DEBUG]修订版:'0'

[11-08 08:45:27.119 3275:3275 F/DEBUG] ABI:'x86_64'

[11-08 08:45:27.119 3275:3275 F/DEBUG] pid:3256,tid:3256,name:m.example.hello >>> com.example.hello <<<

[11-08 08:45:27.119 3275:3275 F/DEBUG]信号6(SIGABRT),代码-6(SI_TKILL),故障添加器--------

[11-08 08:45:27.120 3275:3275 F/DEBUG]中止消息:'[致命:gpu_info_collector_android.cc(193)]无法创建用于获取驱动程序字符串的pbuffer表面.EGL_SUCCESS(3000)'

[11-08 08:45:27.120 3275:3275 F/DEBUG] rax 0000000000000000 rbx 00007ffef7ff9be8 rcx ffffffffffffffff rdx 0000000000000006

[11-08 08:45:27.120 3275:3275 F/DEBUG] rsi 0000000000000cb8 rdi 0000000000000cb8

[11-08 08:45:27.120 3275:3275 F/DEBUG] r8 0000000000000305 r9 00007ffee3659c75 r10 0000000000000008 r11 0000000000000206

[11-08 08:45:27.120 3275:3275 F/DEBUG] r12 0000000000000cb8 r13 0000000000000006 r14 00007ffef69eb000 r15 00007fff5da2f320

[11-08 08:45:27.120 3275:3275 F/DEBUG] cs 0000000000000033 ss 000000000000002b

[11-08 08:45:27.120 3275:3275 F/DEBUG] rip 00007ffef6984b27 rbp 0000000000000058 rsp 00007fff5da2ec88 eflags 0000000000000206

[11-08 08:45:27.120 3275:3275 F/DEBUG]

回溯:

[11-08 08:45:27.120 3275:3275 F/DEBUG]#00 pc 000000000008db27 /system/lib64/libc.so(tgkill + 7)

[11-08 08:45:27.120 3275:3275 F/DEBUG] #01 pc 000000000008a5c1 /system/lib64/libc.so(pthread_kill + 65)

[11-08 08:45:27.120 3275:3275 F/DEBUG] #02 pc 0000000000030241 /system/lib64/libc.so(raise + 17)

[11-08 08:45:27.120 3275:3275 F/DEBUG] #03 pc 000000000002877d /system/lib64/libc.so(abort + 77)

[11-08 08:45:27.120 3275:3275 F/DEBUG] #04 pc 0000000002a93c38 /system/app/webview/webview.apk(offset 0x3c9c000)

[11-08 08:45:27.415 1571:1643 I/BootReceiver]将/ data/tombstones/tombstone_09复制到DropBox(SYSTEM_TOMBSTONE)

[11-08 08:45:27.419 1183:1183 W /] debuggerd:恢复目标3256

[11-08 08:45:27.503 1233:1233 I/Zygote]过程3256由于信号(6)而退出

[11-08 08:45:27.629 1571:3280 W/ActivityManager]强制完成活动com.example.hello/.MainActivity

[11-08 08:45:27.631 1571:3280 W/ActivityManager]在android.os.BinderProxy.transact的android.os.BinderProxy.transactNative(Native Method)暂停android.os.DeadObjectException期间抛出异常(Binder.java: 615)在com.android.server.am.ActivityStack.finishActivityLocked(ActivityStack)的com.android.server.am.ActivityStack.startPausingLocked(ActivityStack.java:1128)的android.app.ApplicationThreadProxy.schedulePauseActivity(ApplicationThreadNative.java:784) .java:3483)位于com.android.server的com.android.server.am.ActivityStack.finishTopRunningActivityLocked(ActivityStack.java:3319)com.android.server.am.ActivityStackSupervisor.finishTopRunningActivityLocked(ActivityStackSupervisor.java:1821). am.AppErrors.handleAppCrashLocked(AppErrors.java:619)位于com.android.server.am.AppErrors.crashApplicationInner(AppErrors.java:357)的com.android.server.am.AppErrors.makeAppCrashingLocked(AppErrors.java:481) at co.android.server.am.AppErrors.crashApplication(AppErrors.java:309)at co m.android.server.am.ActivityManagerService.handleApplicationCrashInner(ActivityManagerService.java:13226)at com.android.server.am.NativeCrashListener $ NativeCrashReporter.run(NativeCrashListener.java:86)

[11-08 08:45:27.631 1226:1226 E/lowmemorykiller]打开错误/ proc/3256/oom_score_adj; 错误号= 2

[11-08 08:45:27.751 1228:1228 D/gralloc]在创建缓冲区的过程中注册缓冲区.这可能会导致内存排序问题.

[11-08 08:45:27.751 1228:1228 E/libEGL]称为未实现的OpenGL ES API

[11-08 08:45:27.751 1228:1228 E/SurfaceFlinger] glCheckFramebufferStatusOES错误1200695526

[11-08 08:45:27.751 1228:1228 E/SurfaceFlinger]在截屏时出现GL_FRAMEBUFFER_COMPLETE_OES错误

[11-08 08:45:27.751 1571:3280 W/WindowManager]截图失败(1440x2560)截图到22015

[11-08 08:45:27.753 1571:1611 W/art]与所有者NativeCrashReport(3280)的长监视器争用在void com.android.server.am.AppErrors.crashApplicationInner(com.android.server.am.ProcessRecord,android .app.ApplicationErrorReport $ CrashInfo)(AppErrors.java:328)waiters = 4 in void com.android.server.am.ActivityManagerService $ AppDeathRecipient.binderDied()for 249ms

[11-08 08:45:27.753 1571:1611 I/ActivityManager]进程com.example.hello(pid 3256)已经死亡

[11-08 08:45:27.755 1571:1647 W/art]与所有者NativeCrashReport(3280)在void com.android.server.am.AppErrors.crashApplicationInner(com.android.server.am.ProcessRecord,android .app.ApplicationErrorReport $ CrashInfo)(AppErrors.java:328)waiters = 6 in void com.android.server.am.ActivityManagerService $ LocalService.notifyAppTransitionFinished()for 126ms

[11-08 08:45:27.763 1571:1931 W/InputMethodManagerService]窗口已经聚焦,忽略了焦点增益:com.android.internal.view.IInputMethodClient$Stub$Proxy@17014ac attribute = null,token = android.os. BinderProxy @ 52c4ec5

[11-08 08:45:28.075 1571:2551 W/art]与所有者android.display(1647)在void com.android.server.wm.WindowAnimator $ 1.doFrame(long)的长监视器争用(WindowAnimator.java:138在netms com.android.server.wm.WindowManagerService.finishDrawingWindow(com.android.server.wm.Session,android.view.IWindow)中的waiters = 1为132ms

[11-08 08:45:28.205 1571:1647 I/WindowManager]销毁com.android.server.wm.WindowStateAnimator.destroySurface:2014 com.android.server所调用的曲面Surface(name = Starting com.example.hello). wm.WindowStateAnimator.destroySurfaceLocked:881 com.android.server.wm.WindowState.removeLocked:1449 com.android.server.wm.WindowManagerService.removeWindowInnerLocked:2478 com.android.server.wm.AppWindowToken.destroySurfaces:365 com.android. server.wm.WindowStateAnimator.finishExit:565 com.android.server.wm.AppWindowAnimator.stepAnimationLocked:427 com.android.server.wm.WindowAnimator.updateAppWindowsLocked:196

[11-08 08:45:30.183 1571:1869 E/TaskPersister]访问最近目录的文件错误(目录不存在？).

这些也无济于事.

科尔多瓦你好世界的应用程序崩溃

科尔多瓦"你好世界"的应用程序将无法显示

Answer 1

我CPU/ABI从Intel Atom(x86_64)更改为Google API Intel Atom(x86_64).它确实有效.