HarmonyOS鸿蒙Next中應用發生閃退 死機在 libarengine_core.z.so

HarmonyOS鸿蒙Next中應用發生閃退 死機在 libarengine_core.z.so 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: Build info:LMR-AL10 6.0.0.50(SP22C00E42R9P3log) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: Timestamp:2025-12-10 18:40:35.450 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: Pid:58164 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: Uid:20020212 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: Process name:com.xunwei.finding 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: Process life time:201s 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: Process Memory(kB): 389865(Rss) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: Reason:Signal:SIGSEGV(SEGV_ACCERR)@0x0000005b44c41108 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: Fault thread info: 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: Tid:63168, Name:OS_FFRT_2_12 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: #00 pc 0000000000202614 /system/lib64/platformsdk/libarengine_core.z.so(HsdkDataObserver::AlgMgrDataRecycleCallback(void*, HxrAlgorithmData*)+128)(838a8ad278a5b7433f32830dd1667c14) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: #01 pc 00000000001b6b78 /system/lib64/platformsdk/libarengine_core.z.so(HXRSDK::AlgorithmManagerImpl::DataRecycleCallback(HxrAlgorithmData*)+164)(838a8ad278a5b7433f32830dd1667c14) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: #02 pc 00000000001abb9c /system/lib64/platformsdk/libarengine_core.z.so(HXRSDK::Algorithm::RemoveDataReference(void*, HxrAlgorithmData*)+192)(838a8ad278a5b7433f32830dd1667c14) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: #03 pc 000000000022b2e4 /system/lib64/platformsdk/libarengine_core.z.so(PreDataMatchImpl::ClearFragmentsBeforeTSInTheCache(std::__h::basic_string<char, std::__h::char_traits<char>, std::__h::allocator<char>> const&, unsigned long)+168)(838a8ad278a5b7433f32830dd1667c14) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: #04 pc 000000000022adb0 /system/lib64/platformsdk/libarengine_core.z.so(PreDataMatchImpl::ProcessMatchedData(HxrAlgorithmData&, HxrAlgorithmData&, HsdkPreDataMatchConfig const&)+520)(838a8ad278a5b7433f32830dd1667c14) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: #05 pc 000000000022a6bc /system/lib64/platformsdk/libarengine_core.z.so(PreDataMatchImpl::PushData(HxrAlgorithmData*)+888)(838a8ad278a5b7433f32830dd1667c14) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: #06 pc 0000000000229294 /system/lib64/platformsdk/libarengine_core.z.so(DataMatchManager::PushData(HxrAlgorithmData*)+588)(838a8ad278a5b7433f32830dd1667c14) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: #07 pc 00000000001addc0 /system/lib64/platformsdk/libarengine_core.z.so(HXRSDK::Algorithm::PushData(std::__h::shared_ptr<HxrAlgorithmData> const&)+256)(838a8ad278a5b7433f32830dd1667c14) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: #08 pc 00000000001b81bc /system/lib64/platformsdk/libarengine_core.z.so(HXRSDK::AlgorithmManagerImpl::PushData(std::__h::shared_ptr<HxrAlgorithmData> const&)+1148)(838a8ad278a5b7433f32830dd1667c14) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: #09 pc 0000000000201ab4 /system/lib64/platformsdk/libarengine_core.z.so(HsdkDataObserver::PushData(std::__h::shared_ptr<HxrAlgorithmData> const&)+372)(838a8ad278a5b7433f32830dd1667c14) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: #10 pc 00000000001ffb20 /system/lib64/platformsdk/libarengine_core.z.so(HsdkDataManager::ThreadLoop()+692)(838a8ad278a5b7433f32830dd1667c14) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: #11 pc 000000000024e52c /system/lib64/platformsdk/libarengine_core.z.so(Thread::Loop(void*)+80)(838a8ad278a5b7433f32830dd1667c14) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: #12 pc 000000000024f9f8 /system/lib64/platformsdk/libarengine_core.z.so(838a8ad278a5b7433f32830dd1667c14) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: #13 pc 000000000008eac0 /system/lib64/ndk/libffrt.so(ffrt::CPUEUTask::Execute()+156)(d0c3d1555f7daa3417de6f857a4fdba1) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: #14 pc 000000000006005c /system/lib64/ndk/libffrt.so(CoStartEntry(void*)+40)(d0c3d1555f7daa3417de6f857a4fdba1) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: ========SubmitterStacktrace======== 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: #00 pc 00000000000b1cbc /system/lib64/ndk/libffrt.so(d0c3d1555f7daa3417de6f857a4fdba1) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: #01 pc 0000000000013de8 /vendor/lib64/passthrough/libffrt_acc.so(ffrt::HDependenceManager::onSubmit(bool, void*&, ffrt_function_header_t*, ffrt_deps_t const*, ffrt_deps_t const*, ffrt::task_attr_private const*)+244)(de0fb87b166ca00664efd82a608ade69) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: #02 pc 000000000004a4a0 /system/lib64/ndk/libffrt.so(ffrt_submit_h_base+176)(d0c3d1555f7daa3417de6f857a4fdba1) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: #03 pc 000000000024f7d0 /system/lib64/platformsdk/libarengine_core.z.so(ffrt::thread::thread<void* ()(void), Thread*, void, void, void>(void* (&&)(void), Thread*&&)+248)(838a8ad278a5b7433f32830dd1667c14) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: #04 pc 000000000024f230 /system/lib64/platformsdk/libarengine_core.z.so(Thread::Run()+224)(838a8ad278a5b7433f32830dd1667c14) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: #05 pc 00000000001fe17c /system/lib64/platformsdk/libarengine_core.z.so(HsdkDataManager::Start()+228)(838a8ad278a5b7433f32830dd1667c14) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: #06 pc 00000000001f9d7c /system/lib64/platformsdk/libarengine_core.z.so(HsdkExternalHalImpl::Start()+380)(838a8ad278a5b7433f32830dd1667c14) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: #07 pc 000000000020698c /system/lib64/platformsdk/libarengine_core.z.so(HalAdapter::Start()+212)(838a8ad278a5b7433f32830dd1667c14) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: #08 pc 00000000001cf060 /system/lib64/platformsdk/libarengine_core.z.so(HsdkImpl::StartAll()+212)(838a8ad278a5b7433f32830dd1667c14) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: #09 pc 00000000001c0ec4 /system/lib64/platformsdk/libarengine_core.z.so(HsdkImpl::Start()+2380)(838a8ad278a5b7433f32830dd1667c14) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: #10 pc 000000000020af84 /system/lib64/platformsdk/libarengine_core.z.so(HsdkStart(void*)+204)(838a8ad278a5b7433f32830dd1667c14) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: #11 pc 0000000000085444 /system/lib64/platformsdk/libarengine_impl.z.so(HiARInstantSlamDevice::Start()+396)(03b3cf279e872eb7cc3f4fbb8d7e4ff2) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: #12 pc 00000000000a4ee4 /system/lib64/platformsdk/libarengine_impl.z.so(HiARSceneManager::StartWithPreview()+260)(03b3cf279e872eb7cc3f4fbb8d7e4ff2) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: #13 pc 000000000007405c /system/lib64/platformsdk/libarengine_impl.z.so(HiARSessionCore::PerformFirstUpdateLocked()+76)(03b3cf279e872eb7cc3f4fbb8d7e4ff2) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: #14 pc 0000000000074410 /system/lib64/platformsdk/libarengine_impl.z.so(HiARSessionCore::Update(HiARFrame*)+652)(03b3cf279e872eb7cc3f4fbb8d7e4ff2) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: #15 pc 0000000000012fcc /system/lib64/ndk/libarengine_ndk.z.so(HMS_AREngine_ARSession_Update.cfi+124)(b86e21eecad47943638a995f1827e5fa) 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: Registers: 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: x0:0000005c53bef9c0 x1:0000005c4d6f03bc x2:0000005b44c41000 x3:0000000000001000 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: x4:0000005a8e7d12bb x5:0000005a8e7d12bb x6:656e69676e455241 x7:65726f43656e6967 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: x8:0000005c4d5402c4 x9:0000005c4d5402e4 x10:6b6b000000000000 x11:0000005a8fe7b000 12-10 18:40:36.450 63395 63395 I C02D11/DfxFaultLogger: x12:0000000069393664 x13:aaaaaaaa052cfdff x14:000000003b9ac9ff x15:b168005a8e8ea274 12-10 18:40:36.451 63395 63395 I C02D11/DfxFaultLogger: x16:0000005a901f5db0 x17:0000005a8e992b90 x18:0000001e7ffc3440 x19:0000005b44c41000 12-10 18:40:36.451 63395 63395 I C02D11/DfxFaultLogger: x20:0000005c53bef9c0 x21:0000005c4d5717da x22:0000005b2dbede00 x23:0000005c50dd60f8 12-10 18:40:36.451 63395 63395 I C02D11/DfxFaultLogger: x24:0000005c4d56e508 x25:0000005b2dbede00 x26:0000005c4d6378db x27:0000005c4d63b112 12-10 18:40:36.451 63395 63395 I C02D11/DfxFaultLogger: x28:0000007e99ea99e9 x29:0000007e99ea9870 12-10 18:40:36.451 63395 63395 I C02D11/DfxFaultLogger: lr:0000005c4d742748 sp:0000007e99ea9830 pc:0000005c4d742614 12-10 18:40:36.451 63395 63395 I C02D11/DfxFaultLogger: pstate:0000000020001000 esr:0000000092000007 12-10 18:40:36.451 63395 63395 I C02D11/DfxProcessDump: Finish dump stacktrace for com.xunwei.finding(58164:63168).


更多关于HarmonyOS鸿蒙Next中應用發生閃退 死機在 libarengine_core.z.so的实战教程也可以访问 https://www.itying.com/category-93-b0.html

2 回复

鸿蒙Next应用闪退死机在libarengine_core.z.so，通常与图形渲染引擎AR Engine核心库相关。可能原因包括：AR Engine服务异常、应用与系统版本不兼容、或该so库文件损坏。可尝试重启设备，检查系统更新，或确认应用是否为鸿蒙Next专用版本。

更多关于HarmonyOS鸿蒙Next中應用發生閃退 死機在 libarengine_core.z.so的实战系列教程也可以访问 https://www.itying.com/category-93-b0.html


根据提供的日志，应用闪退的直接原因是访问了无效的内存地址（SIGSEGV，SEGV_ACCERR），具体发生在libarengine_core.z.so动态库的HsdkDataObserver::AlgMgrDataRecycleCallback函数中。这是一个典型的野指针或已释放内存访问错误。

从调用栈分析，崩溃发生在AR Engine（libarengine）的数据管理模块内部。线程OS_FFRT_2_12在执行数据回收回调时，尝试访问一个无效的HxrAlgorithmData数据结构指针（地址0x0000005b44c41108），触发了段错误。

这通常指向AR Engine底层库在处理算法数据生命周期时出现了问题。可能的原因包括：

  1. 数据竞争或异步时序问题：在多线程（FFRT）环境下，算法数据对象可能在回调执行时已被另一个线程释放。
  2. AR Engine SDK与系统版本兼容性问题：应用使用的AR Engine SDK版本可能与当前HarmonyOS Next的系统底层库（libarengine_core.z.so）存在不兼容。
  3. AR Session管理不当：应用可能在AR会话（HiARSessionCore）的生命周期（如启动、更新、销毁）管理上存在瑕疵，导致底层引擎状态异常。

由于崩溃栈完全位于系统AR Engine库内部，这通常不是应用层代码的直接错误，而是底层服务的异常。建议检查应用集成的AR Engine SDK版本，并确保其与目标设备的HarmonyOS Next版本完全兼容。同时，审查应用调用AR会话Update、Start、Stop的时序逻辑，确保其符合SDK规范。

回到顶部