HarmonyOS 鸿蒙Next模拟器占用资源巨高,有多少跑满多少!一直在输出报错日志,没有停,不知道运行什么(附上报错日志)

HarmonyOS 鸿蒙Next模拟器占用资源巨高,有多少跑满多少!一直在输出报错日志,没有停,不知道运行什么(附上报错日志)

求助求助!!

报错日志:
01-31 08:45:10.840 329-329/? F libc/ : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xc in tid 329 (cust_init), pid 329 (cust_init)

01-31 08:45:10.955 338-338/? F DEBUG/ : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

01-31 08:45:10.955 338-338/? F DEBUG/ : Build fingerprint: 'HUAWEI/JAD-AN00/HWFCO:12/HUAWEIJAD-AN00/3.1.0.155SP50C00:userdebug/dev-keys'

01-31 08:45:10.955 338-338/? F DEBUG/ : Revision: '0'

01-31 08:45:10.955 338-338/? F DEBUG/ : ABI: 'x86_64'

01-31 08:45:10.955 338-338/? F DEBUG/ : Timestamp: 2024-01-31 08:45:10.930449100+0800

01-31 08:45:10.955 338-338/? F DEBUG/ : Process uptime: 0s

01-31 08:45:10.955 338-338/? F DEBUG/ : Cmdline: /system/bin/cust_init

01-31 08:45:10.955 338-338/? F DEBUG/ : pid: 329, tid: 329, name: cust_init >>> /system/bin/cust_init <<<

01-31 08:45:10.955 338-338/? F DEBUG/ : uid: 0

01-31 08:45:10.955 338-338/? F DEBUG/ : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xc

01-31 08:45:10.955 338-338/? F DEBUG/ : Cause: null pointer dereference

01-31 08:45:10.955 338-338/? F DEBUG/ : rax 0000000000000000 rbx 0000000000000000 rcx 000000000000000c rdx 0000000000000000

01-31 08:45:10.955 338-338/? F DEBUG/ : r8 0000000000000007 r9 0000000000000000 r10 00005e2dbfa26354 r11 00005e2dbf9fd22a

01-31 08:45:10.955 338-338/? F DEBUG/ : r12 0000000000000007 r13 0000000000000000 r14 00005e2dbf9fd22a r15 0000000000000400

01-31 08:45:10.955 338-338/? F DEBUG/ : rdi 000000000000000c rsi 0000000000000073

01-31 08:45:10.955 338-338/? F DEBUG/ : rbp 00005e2dbfa267f0 rsp 00007fffb7c557c8 rip 000078161131e621

01-31 08:45:10.955 338-338/? F DEBUG/ : backtrace:

01-31 08:45:10.955 338-338/? F DEBUG/ : #00 pc 0000000000095621 /apex/com.android.runtime/lib64/bionic/libc.so (strlen+17) (BuildId: 2de37b8aa6e96dd64a6cfa51bd78ae6e)

01-31 08:45:10.955 338-338/? F DEBUG/ : #01 pc 0000000000094aae /system/bin/cust_init (SecVsnprintfImpl+3710) (BuildId: 5fe142fe5d6bb44ad9476509b4ec8734)

01-31 08:45:10.955 338-338/? F DEBUG/ : #02 pc 0000000000093b0d /system/bin/cust_init (vsnprintf_s+61) (BuildId: 5fe142fe5d6bb44ad9476509b4ec8734)

01-31 08:45:10.955 338-338/? F DEBUG/ : #03 pc 00000000000482bc /system/bin/cust_init (RecoveryPrint+460) (BuildId: 5fe142fe5d6bb44ad9476509b4ec8734)

01-31 08:45:10.955 338-338/? F DEBUG/ : #04 pc 0000000000049487 /system/bin/cust_init (HwRecoverySymlinkFile+327) (BuildId: 5fe142fe5d6bb44ad9476509b4ec8734)

01-31 08:45:10.955 338-338/? F DEBUG/ : #05 pc 000000000003d406 /system/bin/cust_init (SymlinkCust+454) (BuildId: 5fe142fe5d6bb44ad9476509b4ec8734)

01-31 08:45:10.955 338-338/? F DEBUG/ : #06 pc 000000000003e579 /system/bin/cust_init (DefaultCust+905) (BuildId: 5fe142fe5d6bb44ad9476509b4ec8734)

01-31 08:45:10.956 338-338/? F DEBUG/ : #07 pc 000000000003ae3d /system/bin/cust_init (main+205) (BuildId: 5fe142fe5d6bb44ad9476509b4ec8734)

01-31 08:45:10.956 338-338/? F DEBUG/ : #08 pc 0000000000090cf9 /apex/com.android.runtime/lib64/bionic/libc.so (__libc_init+89) (BuildId: 2de37b8aa6e96dd64a6cfa51bd78ae6e)

01-31 08:52:40.750 13009-13009/? F linker/ : CANNOT LINK EXECUTABLE "/vendor/bin/hw/android.hardware.usb@1.0-service": library "android.hardware.usb@1.0.so" not found: needed by main executable

01-31 08:55:45.068 15535-15535/? F linker/ : CANNOT LINK EXECUTABLE "/vendor/bin/hw/android.hardware.usb@1.0-service": library "android.hardware.usb@1.0.so" not found: needed by main executable

01-31 08:58:25.415 16589-16589/? E AndroidRuntime/: FATAL EXCEPTION: main

01-31 08:58:25.415 16589-16589/? E AndroidRuntime/: Process: com.huawei.contacts, PID: 16589

01-31 08:58:25.415 16589-16589/? E AndroidRuntime/: java.lang.RuntimeException: Unable to instantiate application com.android.contacts.ContactsApplication package com.huawei.contacts: java.lang.IllegalStateException: failed to attach Application, init bundle manager proxy failed., the coreSa are not ready yet, need to wait until coreSa are readybefore starting the application

...

01-31 09:06:46.495 20510-20510/? E AndroidRuntime/: Process: com.huawei.hiai, PID: 20510

01-31 09:06:46.495 20510-20510/? E AndroidRuntime/: java.lang.RuntimeException: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0

...

01-31 09:07:27.846 15357-15415/? E AmbientLightMonitor/: AmbientLightCollectionData.collect() error!input params out of range: lux=0, durationInMs=6208

01-31 09:07:27.846 15357-15415/? E AmbientLightMonitor/: AmbientLightCollectionData.collect() error!input params out of range: lux=0, durationInMs=6208

01-31 09:07:47.352 15357-15415/? E AmbientLightMonitor/: AmbientLightCollectionData.collect() error!input params out of range: lux=0, durationInMs=5239

01-31 09:07:47.352 15357-15415/? E AmbientLightMonitor/: AmbientLightCollectionData.collect() error!input params out of range: lux=0, durationInMs=5239

01-31 09:08:32.322 15357-15415/? E AmbientLightMonitor/: AmbientLightCollectionData.collect() error!input params out of range: lux=0, durationInMs=6258

01-31 09:08:32.323 15357-15415/? E AmbientLightMonitor/: AmbientLightCollectionData.collect() error!input params out of range: lux=0, durationInMs=6258

01-31 09:08:37.054 650-650/? E thermal/-daemon: logPower_print not support

01-31 09:01:11.870 17049-18865/? E 03900/Ace: [multimodal_manager.cpp(OpenChannel)-(1)] fail to get subscriber to register callback

更多关于HarmonyOS 鸿蒙Next模拟器占用资源巨高,有多少跑满多少!一直在输出报错日志,没有停,不知道运行什么(附上报错日志)的实战教程也可以访问 https://www.itying.com/category-93-b0.html

2 回复

你这应该是应用崩溃了,有的代码一直还在跑,导致一直跑日志

更多关于HarmonyOS 鸿蒙Next模拟器占用资源巨高,有多少跑满多少!一直在输出报错日志,没有停,不知道运行什么(附上报错日志)的实战系列教程也可以访问 https://www.itying.com/category-93-b0.html


根据你描述的情况,鸿蒙Next模拟器占用资源过高且持续输出报错日志,可能是以下原因之一:

  1. 模拟器配置问题:模拟器可能未正确配置,导致资源占用过高。检查模拟器的CPU、内存等设置,确保其与主机硬件兼容。

  2. 应用或服务异常:模拟器中运行的某个应用或服务可能存在异常,导致资源被大量占用。检查日志中是否有特定应用或服务的报错信息。

  3. 模拟器版本问题:当前使用的模拟器版本可能存在已知的Bug或性能问题。尝试更新到最新版本,查看问题是否解决。

  4. 系统资源冲突:模拟器可能与主机系统的某些资源发生冲突,导致资源占用异常。检查主机系统的资源使用情况,关闭不必要的后台进程。

  5. 日志输出配置:模拟器的日志输出配置可能存在问题,导致日志输出过多。检查日志级别设置,调整至合适的级别。

建议根据报错日志中的具体信息,进一步排查问题的根源。

回到顶部