HarmonyOS鸿蒙Next 3002 SIGABRT

HarmonyOS鸿蒙Next 3002 SIGABRT

honor pad5 ,鸿蒙2.0.0,运行一段时间闪退

其他安卓设备不闪退

错误内容:

#00 pc 0000000000022ed0 /system/lib64/libc.so (abort+116) [arm64-v8a::4dbabceb1f68056f4d0f9b075ef646f7]

#01 pc 0000000000482c64 /system/lib64/libart.so (art::Runtime::Abort(char const*)+1196) [arm64-v8a::e1f40cc714e9bc79de4b7b8c2139aa86]

#02 pc 0000000000008d20 /system/lib64/libbase.so (android::base::LogMessage::~LogMessage()+800) [arm64-v8a::366e5f02affb29a6ea789d0516fcf36a]

#03 pc 00000000002f2aa8 /system/lib64/libart.so (art::JavaVMExt::JniAbort(char const*, char const*)+1640) [arm64-v8a::e1f40cc714e9bc79de4b7b8c2139aa86]

#04 pc 000000000035e6ac /system/lib64/libart.so (art::JNI::GetIntField(_JNIEnv*, _jobject*, _jfieldID*)+876) [arm64-v8a::e1f40cc714e9bc79de4b7b8c2139aa86]

#05 pc 000000000001e1b0 /system/lib64/libopenjdk.so (FileDispatcherImpl_preClose0+24) [arm64-v8a::d57340a5ff30693200cf1a06eade29bc]

#06 pc 000000000013c62c /system/framework/arm64/boot.oat [arm64-v8a::07055c7c4a975b2113e3cadf549f8d1c]

java:

sun.nio.ch.SocketDispatcher.preClose(SocketDispatcher.java:69)

sun.nio.ch.SocketChannelImpl.implCloseSelectableChannel(SocketChannelImpl.java:885)

java.nio.channels.spi.AbstractSelectableChannel.implCloseChannel(AbstractSelectableChannel.java:234)

java.nio.channels.spi.AbstractInterruptibleChannel.close(AbstractInterruptibleChannel.java:116)

sun.nio.ch.SocketChannelImpl.finalize(SocketChannelImpl.java:939)

java.lang.Daemons$FinalizerDaemon.doFinalize(Daemons.java:250)

java.lang.Daemons$FinalizerDaemon.runInternal(Daemons.java:237)

java.lang.Daemons$Daemon.run(Daemons.java:103)

java.lang.Thread.run(Thread.java:784)

更多关于HarmonyOS鸿蒙Next 3002 SIGABRT的实战教程也可以访问 https://www.itying.com/category-93-b0.html

2 回复

您好,请您通过在线提单进一步解决: https://developer.huawei.com/consumer/cn/support/feedback/#/

感谢您的反馈和支持。

更多关于HarmonyOS鸿蒙Next 3002 SIGABRT的实战系列教程也可以访问 https://www.itying.com/category-93-b0.html


HarmonyOS鸿蒙Next 3002 SIGABRT错误通常是由于程序异常终止引起的,可能是内存访问越界、空指针解引用或资源竞争等问题。建议检查代码逻辑,确保内存管理和线程同步正确。使用调试工具如GDB或LLDB定位问题,查看堆栈跟踪以确定具体原因。同时,确保系统库和依赖项版本兼容,避免因库冲突导致崩溃。

回到顶部