HarmonyOS 鸿蒙Next 真机调试app崩溃问题：之前正常运行，再次安装后点击闪退报cppcrash错误

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

HarmonyOS 鸿蒙Next 真机调试app崩溃问题：之前正常运行，再次安装后点击闪退报cppcrash错误 报错信息如下:

Device info: OpenHarmony 3.2
Build info: OpenHarmony 3.2.9.1
Module name: com.zg.lightning_centralized_monitoring_and_comprehensive_analysis_and_early_warning_platform
Version: 1.0.0
Pid: 3551
Uid: 20040004
Reason: Signal: SIGABRT(SI_QUEUE)@0x0131c94400000ddf from: 3551:20040004

Thread name: com.zg.lightnin

#00 pc 0000000000089fcc /vendor/aosp/system/lib64/libc.so(abort+164) (a85ef5fb74e0282813cd1edb10854577)

#01 pc 0000000000143310 /system/lib64/libark_jsruntime.so (a9838329338e3acbe12d031cfc14bd4c)

#02 pc 00000000002dbdf4 /system/lib64/libark_jsruntime.so(panda::ecmascript::JSPandaFileManager::NewJSPandaFile(panda::panda_file::File const*, std::__h::basic_string<char, std::__h::char_traits<char>, panda::ecmascript::CAddressAllocator<char>> const&)+3116) (a9838329338e3acbe12d031cfc14bd4c)

#03 pc 00000000002d9ea8 /system/lib64/libark_jsruntime.so(panda::ecmascript::JSPandaFileManager::GenerateJSPandaFile(panda::ecmascript::JSThread*, panda::panda_file::File const*, std::__h::basic_string<char, std::__h::char_traits<char>, panda::ecmascript::CAddressAllocator<char>> const&, std::__h::basic_string_view<char, std::__h::char_traits<char>>)+76) (a9838329338e3acbe12d031cfc14bd4c)

#04 pc 00000000002dcfe0 /system/lib64/libark_jsruntime.so(panda::ecmascript::JSPandaFileManager::LoadJSPandaFile(panda::ecmascript::JSThread*, std::__h::basic_string<char, std::__h::char_traits<char>, panda::ecmascript::CAddressAllocator<char>> const&, std::__h::basic_string_view<char, std::__h::char_traits<char>> , void const*, unsigned long, bool)+656) (a9838329338e3acbe12d031cfc14bd4c)

#05 pc 0000000000373734 /system/lib64/libark_jsruntime.so(panda::JSNApi::ExecuteModuleBuffer(panda::ecmascript::EcmaVM*, unsigned char const*, int, std::__h::basic_string<char, std::__h::char_traits<char>, std::__h::allocator<char>> const&, bool)+1012) (a9838329338e3acbe12d031cfc14bd4c)

#06 pc 000000000001e458 /system/lib64/libace_napi_ark.z.so(ArkNativeEngineImpl::RunScriptBuffer(NativeEngine*, char const*, std::__h::vector<unsigned char, std::__h::allocator<unsigned char>>& , bool)+448) (6cbf856c7a0d5909b5fefd8bfbe8189f)

#07 pc 000000000002b124 /system/lib64/libruntime.z.so (a4b9cb973376aa543aa4f0b370d451da)

#08 pc 0000000000029c24 /system/lib64/libruntime.z.so (a4b9cb973376aa543aa4f0b370d451da)

#09 pc 000000000002aacc /system/lib64/libruntime.z.so (a4b9cb973376aa543aa4f0b370d451da)

#10 pc 0000000000026cdc /system/lib64/libruntime.z.so(OHOS::AbilityRuntime::JsRuntime::LoadModule(std::__h::basic_string<char, std::__h::char_traits<char>, std::__h::allocator<char>> const&, std::__h::basic_string<char, std::__h::char_traits<char>, std::__h::allocator<char>> const&, std::__h::basic_string<char, std::__h::char_traits<char>, std::__h::allocator<char>> const&, bool, bool)+1044) (a4b9cb973376aa543aa4f0b370d451da)

#11 pc 0000000000136c38 /system/lib64/libabilitykit_native.z.so(OHOS::AbilityRuntime::JsAbility::Init(std::__h::shared_ptrOHOS::AppExecFwk::AbilityInfo const&, std::__h::shared_ptrOHOS::AppExecFwk::OHOSApplication, std::__h::shared_ptrOHOS::AppExecFwk::AbilityHandler&, OHOS::sptrOHOS::IRemoteObject const&)+840) (eebe908aae7de383ac236a571f2d0b85)

#12 pc 000000000011f7f8 /system/lib64/libabilitykit_native.z.so(OHOS::AppExecFwk::AbilityImpl::Init(std::__h::shared_ptrOHOS::AppExecFwk::OHOSApplication&, std::__h::shared_ptrOHOS::AppExecFwk::AbilityLocalRecord const&, std::__h::shared_ptrOHOS::AppExecFwk::Ability&, std::__h::shared_ptrOHOS::AppExecFwk::AbilityHandler&, OHOS::sptrOHOS::IRemoteObject const&, std::__h::shared_ptrOHOS::AppExecFwk::ContextDeal&)+1148) (eebe908aae7de383ac236a571f2d0b85)

#13 pc 000000000015e0b0 /system/lib64/libabilitykit_native.z.so(OHOS::AppExecFwk::AbilityThread::Attach(std::__h::shared_ptrOHOS::AppExecFwk::OHOSApplication&, std::__h::shared_ptrOHOS::AppExecFwk::AbilityLocalRecord const&, std::__h::shared_ptrOHOS::AppExecFwk::EventRunner const&, std::__h::shared_ptrOHOS::AbilityRuntime::Context const&)+1808) (eebe908aae7de383ac236a571f2d0b85)

#14 pc 0000000000164808 /system/lib64/libabilitykit_native.z.so(OHOS::AppExecFwk::AbilityThread::AbilityThreadMain(std::__h::shared_ptrOHOS::AppExecFwk::OHOSApplication&, std::__h::shared_ptrOHOS::AppExecFwk::AbilityLocalRecord const&, std::__h::shared_ptrOHOS::AppExecFwk::EventRunner const&, std::__h::shared_ptrOHOS::AbilityRuntime::Context const&)+588) (eebe908aae7de383ac236a571f2d0b85)

#15 pc 0000000000074bdc /system/lib64/libappkit_native.z.so(OHOS::AppExecFwk::MainThread::HandleLaunchAbility(std::__h::shared_ptrOHOS::AppExecFwk::AbilityLocalRecord const&)+624) (b49b5c3478983a77b1ca0544d8208e4c)

#16 pc 00000000000815ec /system/lib64/libappkit_native.z.so (b49b5c3478983a77b1ca0544d8208e4c)

#17 pc 000000000000e484 /system/lib64/platformsdk/libeventhandler.z.so(OHOS::AppExecFwk::EventHandler::DistributeEvent(std::__h::unique_ptr<OHOS::AppExecFwk::InnerEvent, void ()(OHOS::AppExecFwk::InnerEvent)> const&)+548) (b03358f302bd622ee0d90ce25d8fac54)

#18 pc 0000000000017964 /system/lib64/platformsdk/libeventhandler.z.so (b03358f302bd622ee0d90ce25d8fac54)

#19 pc 000000000001647c /system/lib64/platformsdk/libeventhandler.z.so(OHOS::AppExecFwk::EventRunner::Run()+92) (b03358f302bd622ee0d90ce25d8fac54)

#20 pc 0000000000077db0 /system/lib64/libappkit_native.z.so(OHOS::AppExecFwk::MainThread::Start()+380) (b49b5c3478983a77b1ca0544d8208e4c)

#21 pc 0000000000012df8 /system/bin/appspawn (b4a21b05365c312a5b9cdc8dedb92d09)

#22 pc 0000000000013064 /system/bin/appspawn (b4a21b05365c312a5b9cdc8dedb92d09)

#23 pc 0000000000012600 /system/bin/appspawn (b4a21b05365c312a5b9cdc8dedb92d09)

#24 pc 000000000002b660 /system/lib64/libbegetutil.z.so (42e6fc89ee1f8c790bbe8884d7e7c23f)

#25 pc 000000000002b2c8 /system/lib64/libbegetutil.z.so (42e6fc89ee1f8c790bbe8884d7e7c23f)

#26 pc 00000000000290c4 /system/lib64/libbegetutil.z.so(ProcessEvent+112) (42e6fc89ee1f8c790bbe8884d7e7c23f)

#27 pc 0000000000028bec /system/lib64/libbegetutil.z.so (42e6fc89ee1f8c790bbe8884d7e7c23f)

#28 pc 00000000000118c0 /system/bin/appspawn (b4a21b05365c312a5b9cdc8dedb92d09)

#29 pc 000000000000f9c0 /system/bin/appspawn (b4a21b05365c312a5b9cdc8dedb92d09)

#30 pc 0000000000082304 /vendor/aosp/system/lib64/libc.so(__libc_init+96) (a85ef5fb74e0282813cd1edb10854577)


更多关于HarmonyOS 鸿蒙Next 真机调试app崩溃问题：之前正常运行，再次安装后点击闪退报cppcrash错误的实战系列教程也可以访问 https://www.itying.com/category-93-b0.html

4 回复

这个问题通过在线提单进一步解决：https://developer.huawei.com/consumer/cn/support/feedback/#/，感谢您的反馈和支持

更多关于HarmonyOS 鸿蒙Next 真机调试app崩溃问题：之前正常运行，再次安装后点击闪退报cppcrash错误的实战系列教程也可以访问 https://www.itying.com/category-93-b0.html


学习，

HarmonyOS Next真机调试时出现cppcrash错误，可能是由于以下原因之一：

  1. 资源文件缺失或损坏：检查应用的资源文件是否完整，确保在重新安装过程中没有文件丢失或损坏。

  2. 依赖库版本不匹配：确认应用所依赖的库版本与当前系统版本兼容，版本不匹配可能导致崩溃。

  3. 内存管理问题：检查应用是否存在内存泄漏或非法内存访问，特别是在使用C++代码时。

  4. 日志分析：通过查看崩溃日志，定位具体的崩溃点和原因，日志通常包含详细的调用栈信息。

  5. 权限问题：确保应用在重新安装后获得了所有必要的权限，权限缺失可能导致应用无法正常运行。

  6. 系统更新：检查设备系统是否进行了更新，系统更新可能引入了不兼容的变更。

  7. 缓存问题：清理应用的缓存数据，重新安装后缓存数据可能引发问题。

  8. 代码变更：确认在重新安装前是否有代码变更，特别是与崩溃相关的模块。

通过以上步骤，可以逐步排查并解决cppcrash错误。

鸿蒙Next真机调试时出现cppcrash错误，可能由于以下原因导致：

  1. 代码中存在内存泄漏或非法内存访问；
  2. 依赖库版本不兼容；
  3. 系统资源不足。

建议检查代码中的内存管理，确保依赖库与鸿蒙Next兼容，并清理系统资源后重新安装调试。同时，查看日志获取更多错误信息，便于定位问题。

回到顶部
AI 助手
你好，我是IT营的 AI 助手
您可以尝试点击下方的快捷入口开启体验！