OpenHarmony开发者论坛

标题: 移植OpenHarmony后将appspawn 进程启动后反复如下打印不知道为什么 [打印本页]

作者: xuxiyang    时间: 2024-5-15 14:15
标题: 移植OpenHarmony后将appspawn 进程启动后反复如下打印不知道为什么
[md]01-01 00:00:22.188 2161 2161 D 01100/bundlems: DeserializeInnerBundleInfos finished
01-01 00:00:22.199 2161 2161 E 00000/(null): Should SetUIContent before slice active
01-01 00:00:22.199 2161 2161 I 00000/(null): [appspawn_service.c:47][appspawn] get service name appspawn.
01-01 00:00:22.199 997 797 I 01518/IPCRPC: ipc skeleton wait for proxy init
01-01 00:00:22.199 997 797 I 01518/IPCRPC: current handle already exist
01-01 00:00:22.203 1076 798 E 00000/(null): [main.c:42]SignalHandler sigPID 2161.
01-01 00:00:23.159 989 797 D 01300/abilityms: AbilityAttachTask::Execute(33): start
01-01 00:00:23.159 989 797 E 01518/IPCRPC: first add death callback for handle = 7.
01-01 00:00:23.159 989 797 D 01300/abilityms: AbilityThreadClient::Initialize(68): token(98784248401) bundleName(com.huawei.launcher) success
01-01 00:00:23.159 989 797 E 00000/(null): Perm file not exists.
01-01 00:00:23.159 989 797 D 01300/abilityms: AbilityThreadClient::AppInitTransaction(113): start
01-01 00:00:23.159 2269 2269 I 00000/(null): Start app init
01-01 00:00:23.161 2269 2269 I 00000/(null): RegisterAbility MainAbility
01-01 00:00:23.161 2269 2269 I 00000/(null): RegisterAbilitySlice MainAbilitySlice
01-01 00:00:23.161 2269 2269 I 00000/(null): Set env ret: 0, App init end
01-01 00:00:23.161 989 797 D 01300/abilityms: AbilityThreadClient::AbilityTransaction(90): start
01-01 00:00:23.161 2269 2269 I 00000/(null): perform transact ability state to [3]
01-01 00:00:23.161 2269 2269 I 00000/(null): Create ability success [MainAbility]
01-01 00:00:23.161 2269 2269 I 00000/(null): Hal and UI init
01-01 00:00:23.161 2269 2269 I 00000/(null): [appspawn_service.c:47][appspawn] get service name appspawn.
01-01 00:00:23.162 997 797 D 01800/Samgr: Judge Auth<WMS, (null)> ret:0
01-01 00:00:23.162 2269 2269 I 01518/IPCRPC: ipc skeleton wait for proxy init
01-01 00:00:23.162 2269 2269 E 01518/IPCRPC: first add death callback for handle = 2.
01-01 00:00:23.162 2269 2269 I 01800/Samgr: Create remote sa proxy<WMS, (null)>!
01-01 00:00:23.162 2011 804 I 01518/IPCRPC: ipc skeleton wait for proxy init
01-01 00:00:23.162 2011 804 E 01518/IPCRPC: first add death callback for handle = 2.
01-01 00:00:23.162 2269 2269 I 02500/HDF_LOG_TAG: GfxInitialize: gfx initialize success
01-01 00:00:23.171 2269 2269 I 00000/(null): Create UITaskPost thread
01-01 00:00:23.171 2269 2269 I 00000/(null): Ability Init
01-01 00:00:23.171 2269 2269 I 00000/(null): Ability OnStart
01-01 00:00:23.171 2269 2269 I 00000/(null): AbilitySlice Init
01-01 00:00:23.171 2269 2269 I 00000/(null): AbilitySlice OnStart
01-01 00:00:23.172 2269 2269 I 00000/(null): [appspawn_service.c:47][appspawn] get service name appspawn.
01-01 00:00:23.173 2272 2269 I 00000/(null): start UITaskPost loop
01-01 00:00:23.173 997 797 D 01800/Samgr: Judge Auth<bundlems, BmsFeature> ret:0
01-01 00:00:23.173 2269 2269 I 01518/IPCRPC: ipc skeleton wait for proxy init
01-01 00:00:23.173 2269 2269 I 01518/IPCRPC: current handle already exist
01-01 00:00:23.173 2269 2269 I 01800/Samgr: Create remote sa proxy<bundlems, BmsFeature>!
01-01 00:00:23.173 997 797 I 01518/IPCRPC: ipc skeleton wait for proxy init
01-01 00:00:23.173 2269 2269 I 00000/(null): [appspawn_service.c:47][appspawn] get service name appspawn.
01-01 00:00:23.174 2269 2269 D 01100/bundlems: DeserializeInnerBundleInfos start
01-01 00:00:23.175 2269 2269 D 01100/bundlems: DeserializeInnerBundleInfos finished
01-01 00:00:23.186 2269 2269 E 00000/(null): Should SetUIContent before slice active
01-01 00:00:23.186 2269 2269 I 00000/(null): [appspawn_service.c:47][appspawn] get service name appspawn.
01-01 00:00:23.186 997 797 I 01518/IPCRPC: ipc skeleton wait for proxy init
01-01 00:00:23.186 997 797 I 01518/IPCRPC: current handle already exist
01-01 00:00:23.190 1076 798 E 00000/(null): [main.c:42]SignalHandler sigPID 2269.
01-01 00:00:23.190 990 797 E 01518/IPCRPC: SA dead delete it, handle = 8.
01-01 00:00:23.190 2011 804 I 01518/IPCRPC: dead binder now call SendObituary.
01-01 00:00:23.190 2011 804 E 01518/IPCRPC: SA dead delete it, handle = 1.
01-01 00:00:23.191 997 797 I 01518/IPCRPC: dead binder now call SendObituary.
01-01 00:00:23.191 997 797 E 01518/IPCRPC: SA dead delete it, handle = 7.
01-01 00:00:23.191 997 797 E 01300/abilityms: AbilityMgrFeature::AppDeathNotify(585): com.huawei.launcher AppDeathNotify called
01-01 00:00:23.191 989 797 D 01300/abilityms: AbilityMgrHandler::RestartApp(242): start com.huawei.launcher
01-01 00:00:23.191 989 797 D 01300/abilityms: AppRestartTask::Execute(30): start
01-01 00:00:24.181 2381 2381 E 00000/(null): [appspawn_process.c:160]SetCapabilities appProperty->message.capsCnt 0
01-01 00:00:24.181 2381 2381 I 00000/(null): [appspawn_server.c:187]App timeused 2381 181 ns.
01-01 00:00:24.181 2381 2381 I 00000/(null): [appspawn_process.c:166]AbilityMain
01-01 00:00:24.181 2381 2381 I 00000/(null): [appspawn_process.c:170][appspawn] invoke, msg<com.huawei.launcher,103079215753,104,104>
01-01 00:00:24.181 2381 2381 I 01518/IPCRPC: ResetIpc called
[/md]
作者: balckjojo    时间: 2024-6-3 17:46
这个问题的原因有查到么
作者: balckjojo    时间: 2024-6-4 17:02
回复 balckjojo: 今天查到原因是luancher.hap在加载出错之后会反复加载,就形成一直打印的现象。但是为什么luancher.hap会加载出错问题未知
作者: xuxiyang    时间: 2024-6-4 17:13
回复 balckjojo: 要启动UI task
作者: balckjojo    时间: 2024-6-4 19:57
回复 xuxiyang: 请问这里的UItask指的是display相关么,我这边也是没有显示的,没有显示是不是开启不了UItask。
作者: balckjojo    时间: 2024-6-5 10:25
回复 xuxiyang: 可以请教一下如何开启UItask么。指的是如下的代码段么
  1.     "subsystems": [
  2.       {
  3.         "subsystem": "arkui",
  4.         "components": [
  5.           { "component": "ace_engine_lite", "features":[ "" ] },
  6.           { "component": "ui_lite", "features":[ "enable_graphic_font = true" ] }
  7.         ]
  8.       },
复制代码

作者: xuxiyang    时间: 2024-6-6 11:16
回复 balckjojo: 你要把window 和图形的驱动都要完成,display 的hal 也要完成
作者: balckjojo    时间: 2024-6-6 13:34
回复 xuxiyang: 好的,多谢了。我这边的系统无display,暂时不加载luncher.hap对系统其他功能没有影响吧。
作者: xuxiyang    时间: 2024-6-6 14:34
回复 balckjojo: 你是小型还是standard? 你要删掉luncher.hap吗
作者: balckjojo    时间: 2024-6-6 16:14
回复 xuxiyang: 小型系统。现在的计划是不加载luncher.hap,调试其他功能。后续display调试完成之后再加载luncher.hap。




欢迎光临 OpenHarmony开发者论坛 (https://forums.openharmony.cn/) Powered by Discuz! X3.5