华为mate 60(BRA-AL00)android12手机APP在HarmonyOS鸿蒙Next中的crash问题
华为mate 60(BRA-AL00)android12手机APP在HarmonyOS鸿蒙Next中的crash问题 团队开发的app在mate60 64位适配有问题,偶现crash,但无法分析具体原因
有几个点帮忙确认下:
- 出问题的原因,从栈上能看出来吗,具体因为app的哪个调用导致的?
- 目前app,仅在mate 60上出现该问题,mate 60 针对该库是否有特殊修改?
感谢。
原始crash栈如下:
04-30 14:27:46.859 7467 7467 E DEBUG : failed to read /proc/uptime: Permission denied
04-30 14:27:47.204 7467 7467 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
04-30 14:27:47.204 7467 7467 F DEBUG : Build fingerprint: 'HUAWEI/BRA-AL00/HWBRA:12/HUAWEIBRA-AL00/104.2.0.172C00:user/release-keys'
04-30 14:27:47.204 7467 7467 F DEBUG : Revision: '0'
04-30 14:27:47.204 7467 7467 F DEBUG : ABI: 'arm64'
04-30 14:27:47.204 7467 7467 F DEBUG : Timestamp: 2025-04-30 14:27:46.859552195+0800
04-30 14:27:47.204 7467 7467 F DEBUG : Process uptime: 0s
04-30 14:27:47.204 7467 7467 F DEBUG : Cmdline: com.eastcom.mcx
04-30 14:27:47.204 7467 7467 F DEBUG : pid: 19428, tid: 26993, name: RenderThread >> com.eastcom.mcx <<
04-30 14:27:47.204 7467 7467 F DEBUG : uid: 10240
04-30 14:27:47.204 7467 7467 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x7af275d00028
04-30 14:27:47.204 7467 7467 F DEBUG : x0 0000007b0632e800 x1 0000007b5e7b7528 x2 0000007b5e630ec4 x3 0000007b782946c0
04-30 14:27:47.204 7467 7467 F DEBUG : x4 0000007afef23ee0 x5 0000007afef23f00 x6 0000007af50c3180 x7 0000007af50c2e00
04-30 14:27:47.204 7467 7467 F DEBUG : x8 00007af275d00000 x9 00007af275d00028 x10 0000000000000001 x11 0000000000000000
04-30 14:27:47.204 7467 7467 F DEBUG : x12 0000007b78296800 x13 0000007b78296480 x14 0000007afef22830 x15 0000007c1e1d0eb8
04-30 14:27:47.204 7467 7467 F DEBUG : x16 0000007b5ea88e48 x17 0000007c1e1a4d60 x18 0000007af1336000 x19 0000007b0632e800
04-30 14:27:47.204 7467 7467 F DEBUG : x20 0000007af52477ff x21 0000000000000000 x22 0000000000000008 x23 0000000000000001
04-30 14:27:47.204 7467 7467 F DEBUG : x24 0000007c2b849000 x25 0000007af56673c0 x26 0000007b062ad000 x27 000000009e406cb5
04-30 14:27:47.204 7467 7467 F DEBUG : x28 431bde82d7b634db x29 0000007b065a48a0
04-30 14:27:47.204 7467 7467 F DEBUG : lr 0000007b5e7afc90 sp 0000007b065a47e0 pc 0000007b5e7b757c pst 0000000060001000
04-30 14:27:47.204 7467 7467 F DEBUG : backtrace:
04-30 14:27:47.204 7467 7467 F DEBUG : #00 pc 00000000003b757c /vendor/lib64/egl/libGLES_v200.so (BuildId: 47b762f712562a9e1e7ad091f40d10e5)
04-30 14:27:47.204 7467 7467 F DEBUG : #01 pc 00000000003afc8c /vendor/lib64/egl/libGLES_v200.so (BuildId: 47b762f712562a9e1e7ad091f40d10e5)
04-30 14:27:47.205 7467 7467 F DEBUG : #02 pc 0000000000416288 /system/lib64/libhwui.so (GrGpuResource::release()+928) (BuildId: cada286fa86c19aa174b1255a4570113)
04-30 14:27:47.205 7467 7467 F DEBUG : #03 pc 00000000004b0958 /system/lib64/libhwui.so (GrGpuResource::CacheAccess::release()+20) (BuildId: cada286fa86c19aa174b1255a4570113)
04-30 14:27:47.205 7467 7467 F DEBUG : #04 pc 000000000042c390 /system/lib64/libhwui.so (GrDirectContext::performDeferredCleanup(std::__1::chrono::duration<long long, std::__1::ratio<1l, 1000l>> &, bool)+988) (BuildId: cada286fa86c19aa174b1255a4570113)
04-30 14:27:47.205 7467 7467 F DEBUG : #05 pc 0000000000612c60 /system/lib64/libhwui.so (android::uirenderer::renderthread::CacheManager::trimStaleResources()+92) (BuildId: cada286fa86c19aa174b1255a4570113)
04-30 14:27:47.205 7467 7467 F DEBUG : #06 pc 000000000061728c /system/lib64/libhwui.so (std::__1::__function::__func<decltype(fp()) android::uirenderer::WorkQueue::runSync<android::uirenderer::renderthread::RenderProxy::stopDrawing()::$_27>(android::uirenderer::renderthread::RenderProxy::stopDrawing()::$_27&&)::'lambda'(), std::__1::allocator<decltype(fp()) android::uirenderer::WorkQueue::runSync<android::uirenderer::renderthread::RenderProxy::stopDrawing()::$_27>(android::uirenderer::renderthread::RenderProxy::stopDrawing()::$_27&&)::'lambda'()> , void ()>::operator()() (.96b4c1c9e93b14a25d20002b0ed04af6)+88) (BuildId: cada286fa86c19aa174b1255a4570113)
04-30 14:27:47.205 7467 7467 F DEBUG : #07 pc 000000000050e834 /system/lib64/libhwui.so (android::uirenderer::renderthread::RenderThread::threadLoop()+628) (BuildId: cada286fa86c19aa174b1255a4570113)
04-30 14:27:47.205 7467 7467 F DEBUG : #08 pc 0000000000014084 /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+284) (BuildId: 47a3fb6886677f05caad528b805ffd54)
04-30 14:27:47.205 7467 7467 F DEBUG : #09 pc 00000000000fc938 /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+176) (BuildId: 025750b459d203200a1fcf14928b1078)
04-30 14:27:47.205 7467 7467 F DEBUG : #10 pc 000000000009a840 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+40) (BuildId: 025750b459d203200a1fcf14928b1078)
更多关于华为mate 60(BRA-AL00)android12手机APP在HarmonyOS鸿蒙Next中的crash问题的实战教程也可以访问 https://www.itying.com/category-93-b0.html
1 回复
更多关于华为mate 60(BRA-AL00)android12手机APP在HarmonyOS鸿蒙Next中的crash问题的实战系列教程也可以访问 https://www.itying.com/category-93-b0.html
华为Mate 60(BRA-AL00)在HarmonyOS Next中出现的APP崩溃问题,可能源于系统与应用的兼容性差异。建议首先检查应用是否为最新版本,并确保HarmonyOS系统已更新至最新。若问题持续,可尝试清除应用缓存或重新安装应用。如仍无法解决,建议联系应用开发者或华为客服,获取更专业的技术支持。同时,关注华为官方社区或论坛,了解是否有其他用户遇到类似问题及解决方案。