移动端三维滑动场景无响应。

0 投票
2020-06-23 15:50:31.725 21952-27777/com.smartcity.sm3d.firecontrol E/OGRE: OGRE EXCEPTION(2:InvalidParametersException): Framebuffer incomplete or other FBO status error in GLES2FrameBufferObject::initialise at E:\AR\OGRE1.9_ES3\RenderSystems\GLES2\src\OgreGLES2FrameBufferObject.cpp (line 267)

平板是 HUAWEIMatePad Pro 调试状态下会出现这种错误,界面滑动无响应,请问啥原因导致的。
6月 23 分类:  50次浏览 | 用户: kgh0 才疏学浅 (10 分)

1个回答

0 投票
您好,请问一下您使用的iMobile for Android的版本是多少,在什么情况下会出现这个问题呢?直接运行是否会出现无响应
6月 28 用户: 董懿鑫 登峰造极 (5,818 分)
iMobile 10i for Android ,这个看着像是和平板有关  HUAWEIMatePad Pro 就会出现这种渲染ANR问题,HUAWEI M5、 M6平板好像没有这个出现这个问题。你们用MatePad Pro (型号:MRX-AL09  版本号:10.1.0.135(C00E121R1P121) GPU Tyrbo   Android版本:10  内存 6G) 测试下。 这种渲染问题 有时一滑动地图就出现,有时需要滑动一会。
好的,感谢您提出这个问题,我们会测试相应的机型。看是否会出现ANR现象

Logcat:ANR信息:

2020-06-29 14:21:08.963 1263-1716/? E/ActivityManager: ANR in com.smartcity.sm3d.firecontrol (com.smartcity.sm3d.firecontrol/.activity.MainActivity)
    PID: 4080
    Reason: Input dispatching timed out (Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. waitqueue length = 1, head.seq = 128656, Wait queue head age: 6497.0ms.)
    Parent: com.smartcity.sm3d.firecontrol/.activity.MainActivity
    Load: 48.43 / 47.62 / 48.06
    CPU usage from 264554ms to 0ms ago (2020-06-29 14:16:43.360 to 2020-06-29 14:21:07.915) with 99% awake:
      5.4% 4080/usap32: 4.9% user + 0.4% kernel / faults: 503520 minor 520 major
      8.5% 1263/system_server: 4.9% user + 3.6% kernel / faults: 155760 minor 1298 major
      3.6% 8737/adbd: 0.7% user + 2.9% kernel / faults: 20428 minor 2 major
      2.3% 758/surfaceflinger: 1.1% user + 1.1% kernel / faults: 3782 minor 5 major
      2.2% 507/logd: 0.6% user + 1.5% kernel / faults: 505 minor
      1.8% 2083/com.huawei.android.launcher: 1.2% user + 0.6% kernel / faults: 60519 minor 263 major
      1.7% 13206/android.process.media: 1.1% user + 0.5% kernel / faults: 11997 minor 10 major
      1.7% 25885/kworker/u16:20: 0% user + 1.7% kernel / faults: 297 minor
      1.6% 6258/kworker/u16:2: 0% user + 1.6% kernel / faults: 371 minor
      1.3% 25884/kworker/u16:19: 0% user + 1.3% kernel / faults: 7 minor
      1.2% 23499/kworker/u16:6: 0% user + 1.2% kernel / faults: 654 minor
      1.1% 715/android.hardware.graphics.composer@2.2-service: 0.4% user + 0.6% kernel / faults: 572 minor 3 major
      1.1% 8701/chargelogcat-c: 0% user + 1.1% kernel / faults: 86 minor
      1% 1870/com.android.systemui: 0.7% user + 0.3% kernel / faults: 23884 minor 177 major
      0.7% 32582/kworker/u16:1: 0% user + 0.7% kernel / faults: 4 minor
      0.5% 1876/com.huawei.systemmanager:service: 0.3% user + 0.2% kernel / faults: 7899 minor 174 major
      0.5% 1888/com.huawei.iaware: 0.3% user + 0.2% kernel / faults: 8117 minor 62 major
      0.5% 2175/com.huawei.hwid.persistent: 0.3% user + 0.1% kernel / faults: 11856 minor 235 major
      0.4% 176/kswapd0: 0% user + 0.4% kernel
      0.4% 1886/com.huawei.HwOPServer: 0.3% user + 0.1% kernel / faults: 5715 minor 49 major
      0.2% 6613/kworker/u16:3: 0% user + 0.2% kernel
      0.3% 3682/usap32: 0.2% user + 0% kernel / faults: 15633 minor 343 major
      0.4% 1111/pci_rx_hi_task: 0% user + 0.4% kernel
      0.4% 1200/hisi_hcc: 0% user + 0.4% kernel
      0.4% 2169/com.huawei.hwid.core: 0.2% user + 0.1% kernel / faults: 14397 minor 178 major

Traces.txt: 详细错误信息:

"main" prio=5 tid=1 Sleeping
  | group="main" sCount=1 dsCount=0 flags=1 obj=0x72b9e298 self=0xefa03e00
  | sysTid=4080 nice=-10 cgrp=default sched=1073741825/2 handle=0xeffcedc0
  | state=S schedstat=( 2177409378 91144802 1442 ) utm=169 stm=48 core=0 HZ=100
  | stack=0xff172000-0xff174000 stackSize=8192KB
  | held mutexes=
  at java.lang.Thread.sleep(Native method)
  - sleeping on <0x0e403472> (a java.lang.Object)
  at java.lang.Thread.sleep(Thread.java:443)
  - locked <0x0e403472> (a java.lang.Object)
  at java.lang.Thread.sleep(Thread.java:359)
  at android.os.SystemClock.sleep(SystemClock.java:131)
  at com.supermap.realspace.SceneControl.postAction(SceneControl.java:590)
  at com.supermap.realspace.SceneControl.onTouchEvent(SceneControl.java:321)
  at android.view.View.dispatchTouchEvent(View.java:13524)
  at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:3217)
  at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2910)
  at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:3217)
  at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2910)
  at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:3217)
  at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2910)
  at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:3217)
  at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2910)

这个能给先看着处理下么?能处理的话给个新的包啥的
您好,这个问题和设备有关系,我们需要测试下对应的设备。
...