HarmonyOS 鸿蒙Next bugly上报错误SIGABRT,都是华为的机器:Android 10,level 29,HuaWei/EMOTION

发布于 1周前 作者 h691938207 来自 鸿蒙OS

HarmonyOS 鸿蒙Next bugly上报错误SIGABRT,都是华为的机器:Android 10,level 29,HuaWei/EMOTION

Android 10,level 29,HuaWei/EMOTION

# RenderThread(76427)

SIGSEGV(SEGV_MAPERR)

解析原始

1

#00 pc 000000000006bab0 /apex/com.android.runtime/lib64/bionic/libc.so (__memcpy+32) [arm64-v8a::b91c775ccc9b0556e91bc575a2511cd0]

2

#01 pc 00000000000b1af4 /system/lib64/libc++.so (std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::__grow_by_and_replace(unsigned long, unsigned long, unsigned long, unsigned long, unsigned long, unsigned long, char const*)+204) [arm64-v8a::d957c07e50073a9c45a9ca98188a85f7]

3

#02 pc 00000000000b1424 /system/lib64/libc++.so (std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::operator=(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&)+188) [arm64-v8a::d957c07e50073a9c45a9ca98188a85f7]

4

#03 pc 000000000000a244 /system/lib64/libGameGraphicsOpt.so [arm64-v8a::57170ed07e863204dddb98f4c4f22230]

5

#04 pc 00000000000cf7c0 /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+36) [arm64-v8a::b91c775ccc9b0556e91bc575a2511cd0]

6

#05 pc 00000000000721a8 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) [arm64-v8a::b91c775ccc9b0556e91bc575a2511cd0]

7

java:



关于HarmonyOS 鸿蒙Next bugly上报错误SIGABRT,都是华为的机器:Android 10,level 29,HuaWei/EMOTION的问题,您也可以访问:https://www.itying.com/category-93-b0.html 联系官网客服。

11 回复

您好,您的问题需要进一步定位,请您通过在线提单进一步解决:https://developer.huawei.com/consumer/cn/support/feedback/#/,感谢您的反馈和支持。

时至今日,这个问题上报的数量依旧遥遥领先!什么垃圾玩意儿啊!😂

期待HarmonyOS能在未来推出更多针对企业用户的解决方案。

老哥,有解决吗?我最近也遇到了,用户都要疯了

无从解决,很明显是系统bug,不然怎么会只有他家的设备会有上报?

花钱接了专业版的bugly,那边回复也是说是设备的问题,提交工单回复说,不在他们业务范围内,真是服了

HarmonyOS的流畅度和稳定性都让我非常满意,值得推荐给大家。

这个问题有结论吗,我这边也遇到了。bugly崩溃每天都是 top1

android 10 华为鸿蒙

#00 pc 000000000006bab0 /apex/com.android.runtime/lib64/bionic/libc.so (__memcpy+32) [arm64-v8a::b91c775ccc9b0556e91bc575a2511cd0]

2

#01 pc 00000000000b1af4 /system/lib64/libc++.so (std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::__grow_by_and_replace(unsigned long, unsigned long, unsigned long, unsigned long, unsigned long, unsigned long, char const*)+204) [arm64-v8a::d957c07e50073a9c45a9ca98188a85f7]

3

#02 pc 00000000000b1424 /system/lib64/libc++.so (std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::operator=(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&)+188) [arm64-v8a::d957c07e50073a9c45a9ca98188a85f7]

4

#03 pc 000000000000a244 /system/lib64/libGameGraphicsOpt.so [arm64-v8a::57170ed07e863204dddb98f4c4f22230]

5

#04 pc 00000000000cf7c0 /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+36) [arm64-v8a::b91c775ccc9b0556e91bc575a2511cd0]

6

#05 pc 00000000000721a8 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) [arm64-v8a::b91c775ccc9b0556e91bc575a2511cd0]

这个问题有结论么?我们也遇到了。。

您好,您的问题需要进一步定位,请您通过在线提单进一步解决:https://developer.huawei.com/consumer/cn/support/feedback/#/,感谢您的反馈和支持。

这种系统崩溃库崩溃应该选择哪个类目来反馈呢?

回到顶部