Wolvic crash on HVR in MeetKai's WebXR demo experience

[lzhangcs]

WebXR demo experience with 3 different worlds which you can go between crashes on Wolvic in HVR during loading of assets. Please try: https://awe-demo-vr.netlify.app/ It works in great on a mobile 2D Browser like HW Browser on the device as well as in the Meta Quest Browser.

Here are additional links to the experiences. Note the Mobile experience is touch screen phone consumption. Not VR. Mobile Demo Links: Louvre : https://awe-demo-fw.netlify.app/?scene=louvre Zen Garden: https://awe-demo-fw.netlify.app/?scene=zen-garden Beach: https://awe-demo-fw.netlify.app/?scene=beach Forest: https://awe-demo-fw.netlify.app/?scene=forest Web Demo Links: Louvre: https://awe-demo-dev.netlify.app/?scene=louvre Zen Garden: https://awe-demo-dev.netlify.app/?scene=zen-garden Beach: https://awe-demo-dev.netlify.app/?scene=beach Forest: https://awe-demo-dev.netlify.app/?scene=forest VR Networked Demo Links: Louvre: https://awe-demo-dev.netlify.app/?scene=louvre Zen Garden: https://awe-demo-dev.netlify.app/?scene=zen-garden Beach: https://awe-demo-dev.netlify.app/?scene=beach Forest: https://awe-demo-dev.netlify.app/?scene=forest VR Non Networked Demo Links: Louvre: https://mk-metaverse-scenes.netlify.app/?scene=louvre Zen Garden: https://mk-metaverse-scenes.netlify.app/?scene=zen-garden Beach: https://mk-metaverse-scenes.netlify.app/?scene=beach Forest: https://mk-metaverse-scenes.netlify.app/?scene=forest

Per developer: He is able to reproduce it only in HVR. There was no error in Wolvic but he got tons of system errors like this one

2022-06-10 11:14:41.168 W/System.err: android.os.DeadObjectException
2022-06-10 11:14:41.168 W/System.err:     at android.os.BinderProxy.transactNative(Native Method)
2022-06-10 11:14:41.168 W/System.err:     at android.os.BinderProxy.transact(BinderProxy.java:535)
2022-06-10 11:14:41.168 W/System.err:     at com.huawei.hvrsdkserverapp.aidl.ArvrRuntimeInternalInterface$Stub$Proxy.getPosture(ArvrRuntimeInternalInterface.java:479)
2022-06-10 11:14:41.168 W/System.err:     at com.huawei.hwvrexternaldevice.interactive.VrInteractiveDeviceManager.getHeadPose(VrInteractiveDeviceManager.java:528)
2022-06-10 11:14:41.168 W/System.err:     at com.huawei.vrframework.VrHelmetExt.getData(VrHelmetExt.java:100)
2022-06-10 11:14:41.168 E/VrHelmetExt: getData failed
2022-06-10 11:14:41.168 E/HvrHelmetExt: [@SDK][HvrHelmetExt.cpp:GetData](120): GetData arrayLen(0) invalid
2022-06-10 11:14:41.168 E/IMM_Helmet: [@SDK][Helmet.cpp:getExtTrackerData](781): dataSize(-1) illegal
2022-06-10 11:14:41.168 E/IMM_Helmet: [@SDK][Helmet.cpp:getTrackerData](705): getExtTrackerData failed
2022-06-10 11:14:41.168 E/IMM_Helmet: [@SDK][Helmet.cpp:getPose](545): getPose error.

With this in mind and knowing that it is not reproducible on Oculus, this looks like the problem is in HVR SDK. Please take a look. Thanks

[dingsing2021]

feedback from HVR team: 报错问题是属于警告类型的，并且与35#异常成对存在，原因在于sdk采集头戴位姿数据并不能保证一直能获取成功，属于警告类型异常，内部已try住，崩溃问题还需要再实际看一下异常日志; The error is a warning type and happened with the 35 # exception. about this warning , it caused by the VR SDK cannot always obtain the posture data. The error is of the warning type and has been tried internally. For the crash problem, it should be need to check the exception log.

[lzhangcs]

Developer found:

I've just tried with Harmony 3.0 and Wolvic 1.1.1. It still takes ages to load, and the device becomes unresponsive sometimes. According to webglreport the max array texture layers is 4096 now.