HarmonyOS 鸿蒙Next 执行run后一直执行 “hvigor DEBUG default Check process is in registry”，有没有遇到的大佬

HarmonyOS 鸿蒙Next 执行run后一直执行 “hvigor DEBUG default Check process is in registry”，有没有遇到的大佬

C:\Users\durban\nodejs\node.exe C:\Users\durban.hvigor\project_caches\a5f4b36c5be69dfef869655b58c445c5\workspace\node_modules@ohos\hvigor\bin\hvigor.js --debug --mode project -p product=default assembleApp

hvigor DEBUG default Daemon process will change b963372e88ad2a13f2e8e6c780cd63708cdfdec6 info with { “pid”:3376, “state”:“stopReq”, “address”:“127.0.0.1”, “cwdPath”:“C:\Users\durban\DevEcoStudioProjects\HelloWorld”, “hvigorVersion”:“2.4.2”, “keyId”:“b963372e88ad2a13f2e8e6c780cd63708cdfdec6”, “nodeParams”:“d41d8cd98f00b204e9800998ecf8427e”, “nodeVersion”:“v16.19.1”, “port”:45000, “lastUsedTime”:1704706615755, “createdBy”:“deveco” } in registry. hvigor DEBUG default client data: { mode: ‘project’, debug: true, prop: [‘product=default’], _: [‘assembleApp’] }. hvigor DEBUG default build start. hvigor DEBUG default Daemon process will change b963372e88ad2a13f2e8e6c780cd63708cdfdec6 info with { “pid”:3376, “state”:“busy”, “address”:“127.0.0.1”, “cwdPath”:“C:\Users\durban\DevEcoStudioProjects\HelloWorld”, “hvigorVersion”:“2.4.2”, “keyId”:“b963372e88ad2a13f2e8e6c780cd63708cdfdec6”, “nodeParams”:“d41d8cd98f00b204e9800998ecf8427e”, “nodeVersion”:“v16.19.1”, “port”:45000, “lastUsedTime”:1704706616963, “createdBy”:“deveco” } in registry. hvigor DEBUG hvigor-init Hvigor init with startParameters:{ hvigorfileTypeCheck: false, parallelExecution: true, incrementalExecution: true, printStackTrace: false, daemon: true } hvigor DEBUG hvigor-init Cache service initialization cost: 3 ms . hvigor DEBUG ValidateUtil Schema C:\Users\durban\DevEcoStudioProjects\HelloWorld\build-profile.json5 success. hvigor DEBUG ValidateUtil Schema C:\Users\durban\DevEcoStudioProjects\HelloWorld\entry\build-profile.json5 success. hvigor DEBUG ohos-dependency-manager Module entry Collected Dependency: hvigor DEBUG ohos-dependency-manager Module entry’s total dependency: 0 hvigor DEBUG find-target-product Find product from build-profile.json: default hvigor DEBUG Hvigor-target-service entry require SDK: toolchains ArkTS hvigor DEBUG Sdk Sdk init in 39 ms hvigor DEBUG hvigor-abstract-process-resource restool module names: entry hvigor DEBUG hvigor-abstract-process-resource restool module names: entry hvigor DEBUG hvigor-abstract-process-resource restool module names: entry hvigor DEBUG hvigor-abstract-process-resource restool module names: entry hvigor DEBUG ohos-dependency-manager Module HelloWorld Collected Dependency: hvigor DEBUG ohos-dependency-manager Module HelloWorld’s total dependency: 0 hvigor DEBUG find-target-product Find product from build-profile.json: default hvigor DEBUG Sdk Sdk init in 30 ms hvigor DEBUG hvigor-make-project-info project has submodules:entry hvigor DEBUG hvigor-configuration Configuration phase cost:191 ms hvigor DEBUG hvigor-task-executor Configuration task cost before running: 202 ms hvigor Finished ::PreBuildApp… after 1 ms hvigor DEBUG hvigor-task-proxy Incremental task entry:default@PreBuild pre-execution cost: 1 ms . hvigor UP-TO-DATE :entry:default@PreBuild…
hvigor DEBUG hvigor-task-proxy Incremental task entry:default@GenerateMetadata pre-execution cost: 6 ms . hvigor UP-TO-DATE :entry:default@GenerateMetadata…
hvigor DEBUG hvigor-task-proxy Incremental task entry:default@MergeProfile pre-execution cost: 2 ms . hvigor UP-TO-DATE :entry:default@MergeProfile…
hvigor Finished :entry:default@BuildNativeWithCmake… after 1 ms hvigor DEBUG hvigor-task-proxy Incremental task entry:default@GenerateLoaderJson pre-execution cost: 2 ms . hvigor UP-TO-DATE :entry:default@GenerateLoaderJson…
hvigor DEBUG hvigor-task-proxy Incremental task entry:default@MakePackInfo pre-execution cost: 4 ms . hvigor UP-TO-DATE :entry:default@MakePackInfo…
hvigor DEBUG hvigor-task-proxy Incremental task entry:default@ProcessProfile pre-execution cost: 1 ms . hvigor UP-TO-DATE :entry:default@ProcessProfile…
hvigor Finished :entry:default@BuildNativeWithNinja… after 1 ms hvigor DEBUG hvigor-task-proxy Incremental task entry:default@ProcessResource pre-execution cost: 1 ms . hvigor UP-TO-DATE :entry:default@ProcessResource…
hvigor DEBUG hvigor-task-proxy Incremental task entry:default@ProcessLibs pre-execution cost: 1 ms . hvigor UP-TO-DATE :entry:default@ProcessLibs…
hvigor DEBUG hvigor-task-proxy Incremental task entry:default@CompileResource pre-execution cost: 8 ms . hvigor UP-TO-DATE :entry:default@CompileResource…
hvigor DEBUG hvigor-task-proxy entry:default@CompileArkTS is not up-to-date, since the task snapshots are different. hvigor DEBUG hvigor-task-proxy Incremental task entry:default@CompileArkTS pre-execution cost: 4 ms . hvigor DEBUG ArkCompile build config: hvigor DEBUG ArkCompile { packageManagerType: ‘ohpm’, localPropertiesPath: ‘C:\Users\durban\DevEcoStudioProjects\HelloWorld\local.properties’, isPreview: false, buildMode: ‘Release’, watchMode: ‘false’, aceProfilePath: ‘C:\Users\durban\DevEcoStudioProjects\HelloWorld\entry\build\default\intermediates\res\default\resources\base\profile’, etsLoaderPath: ‘C:\Users\durban\AppData\Local\Huawei\Sdk\openharmony\9\ets\build-tools\ets-loader’, modulePath: ‘C:\Users\durban\DevEcoStudioProjects\HelloWorld\entry’, needCoverageInsert: false, projectTopDir: ‘C:\Users\durban\DevEcoStudioProjects\HelloWorld’, compileSdkVersion: 9, compatibleSdkVersion: 9, bundleName: ‘com.example.helloworld’, etsLoaderVersion: ‘3.2.12.5’, etsLoaderReleaseType: ‘Release’, aotCompileMode: undefined, apPath: ‘’, entryModuleName: ‘entry’, allModuleNameHash: ‘1043bfc77febe75fafec0c4309faccf1’, aceModuleJsonPath: ‘C:\Users\durban\DevEcoStudioProjects\HelloWorld\entry\build\default\intermediates\res\default\module.json’, appResource: ‘C:\Users\durban\DevEcoStudioProjects\HelloWorld\entry\build\default\intermediates\res\default\ResourceTable.txt’, resourceTableHash: ‘790527e39c8c2be7fbbc762f7966104e’, runtimeOS: ‘HarmonyOS’, sdkInfo: ‘false:9:3.2.12.5:Release’, aceModuleRoot: ‘C:\Users\durban\DevEcoStudioProjects\HelloWorld\entry\src\main\ets’, compileMode: ‘esmodule’, aceSuperVisualPath: ‘C:\Users\durban\DevEcoStudioProjects\HelloWorld\entry\src\main\supervisual’, aceBuildJson: ‘C:\Users\durban\DevEcoStudioProjects\HelloWorld\entry\build\default\intermediates\loader\default\loader.json’, cachePath: ‘C:\Users\durban\DevEcoStudioProjects\HelloWorld\entry\build\default\cache\default\default@CompileArkTS\esmodule\release’, aceModuleBuild: ‘C:\Users\durban\DevEcoStudioProjects\HelloWorld\entry\build\default\intermediates\loader_out\default\ets’, supportChunks: true } hvigor DEBUG hvigor-worker-pool default@CompileArkTS work[6] is submitted. hvigor DEBUG hvigor-worker-pool default@CompileArkTS work[6] is pushed to ready queue. hvigor DEBUG workerDispatcher default@CompileArkTS work[3] dispatched to worker[0] failed: deny one-time work. hvigor DEBUG workerDispatcher default@CompileArkTS work[6] dispatched to worker[0] failed: deny one-time work. hvigor DEBUG workerDispatcher default@CompileArkTS work[1] dispatched to worker[0] failed: deny one-time work. hvigor DEBUG workerDispatcher default@CompileArkTS work[5] dispatched to worker[0] failed: deny one-time work. hvigor DEBUG workerDispatcher default@CompileArkTS work[2] dispatched to worker[0] failed: deny one-time work. hvigor DEBUG workerDispatcher default@CompileArkTS work[4] dispatched to worker[0] failed: deny one-time work. hvigor DEBUG workerDispatcher default@CompileArkTS work[0] dispatched to worker[0] failed: deny one-time work. hvigor DEBUG workerDispatcher A work dispatched to worker[0] failed because unable to get work from ready queue. hvigor DEBUG hvigor-worker-pool default@CompileArkTS work[6] is not dispatched. hvigor DEBUG hvigor-task-proxy entry:default@CompileJS is not up-to-date, since the output file ‘C:\Users\durban\DevEcoStudioProjects\HelloWorld\entry\build\default\intermediates\loader_out\default\js’ does not exist. hvigor DEBUG hvigor-task-proxy Incremental task entry:default@CompileJS pre-execution cost: 3 ms . hvigor Finished :entry:default@CompileJS… after 5 ms hvigor DEBUG default Check process is in registry… hvigor DEBUG default Check process is in registry… hvigor DEBUG default Check process is in registry… hvigor DEBUG default Check process is in registry… hvigor DEBUG default Check process is in registry… 本来是没有debug信息的 我自己加的 就是想开下是哪里卡住 结果看到是“hvigor DEBUG default Check process is in registry” 不清除是什么原因，求助


更多关于HarmonyOS 鸿蒙Next 执行run后一直执行 “hvigor DEBUG default Check process is in registry”，有没有遇到的大佬的实战教程也可以访问 https://www.itying.com/category-93-b0.html

13 回复

2核的电脑也可以了，同样问题得到解决，设置问题，（在客服中报错后工程师回复了）方法如下：

问题在于设置，file>settings>搜索hvigor>将能去掉的对勾都去掉（日志级别调到debug，下面的并行模式，任务增量，还有下面两个都去掉対勾，启用后对内存和cpu有要求，去掉対勾后就对内存和cpu没有限制了）然后build>clean项目，重新构建build>app就可以了，对软件还是不了解，好了！

相同的另一个帖子： 不能编译，compli 后就一直转圈圈-华为开发者论坛 | 华为开发者联盟 https://developer.huawei.com/consumer/cn/forum/topic/0204147459215082071?fid=0101587866109860105&pid=0304148900447632428

更多关于HarmonyOS 鸿蒙Next 执行run后一直执行 “hvigor DEBUG default Check process is in registry”，有没有遇到的大佬的实战系列教程也可以访问 https://www.itying.com/category-93-b0.html


解决了嘛？我也遇到了。该怎么办呢？

问题描述

电脑配置低了 内存不够的原因

可能原因

  • 系统资源占用过高
  • 运行程序过多
  • 内存条故障

解决方法

  • 关闭不必要的程序
  • 升级内存条
  • 检查硬件是否正常

换了个16G的内存就可以了。

问题在于设置，file>settings>搜索hvigor>将能去掉的对勾都去掉（日志级别调到debug，下面的并行模式，任务增量，还有下面两个都去掉対勾，启用后对内存和cpu有要求，去掉対勾后就对内存和cpu没有限制了）。然后build>clean项目，重新构建build>app就可以了。对软件还是不了解，好了！，

在补充下，之前不用的simulator不能用的情况，现在直接报错提示我由于没有满足磁盘空间，不能使用了，安装的时候是50G的，不行了

另外在补充下，本来之前preview一直不能用的情况，现在也可以使用了，我的天，直接就给个硬件需求就好了，别建议，建议就是达不到要求就不行，我看视频上的都是64G了，我的天

有要学HarmonyOS AI的同学吗，联系我：https://www.itying.com/goods-1206.html

问题在于设置，file>settings>搜索hvigor>将能去掉的对勾都去掉（日志级别调到debug，下面的并行模式，任务增量，还有下面两个都去掉対勾，启用后对内存和cpu有要求，去掉対勾后就对内存和cpu没有限制了）然后build>clean项目，重新构建build>app就可以了，对软件还是不了解，好了！

这个问题我自问自答下

我是ubuntu下安装virutialbox 安装的了win10 然后安装了DevEco Studio的

开始我配置的虚拟机是1核4G，能运行但是都无法正常运行

后面我调整了配置，改为4核8G，在进行打包运行就可以了

我以为是偶尔的情况，于是我又调整了配置，改为2核8G，还是不行

最后只有4核8G才可以

所以针对这个情况，我的建议是增加硬件的配置吧

问题在于设置，file>settings>搜索hvigor>将能去掉的对勾都去掉（日志级别调到debug，下面的并行模式，任务增量，还有下面两个都去掉対勾，启用后对内存和cpu有要求，去掉対勾后就对内存和cpu没有限制了）然后build>clean项目，重新构建build>app就可以了，对软件还是不了解，好了！，

在HarmonyOS鸿蒙Next开发过程中，执行run命令后出现“hvigor DEBUG default Check process is in registry”提示，通常与Hvigor构建系统的进程注册检查相关。Hvigor是鸿蒙Next的构建工具，负责编译、打包等任务。该提示表明Hvigor在启动时正在检查相关进程是否已注册到系统中。

可能的原因包括：

  1. 构建缓存问题：构建缓存可能导致Hvigor在启动时无法正确识别进程状态，进而反复检查。可尝试清理构建缓存，重新执行run命令。

  2. 依赖配置问题：项目依赖未正确配置或依赖版本冲突，可能导致Hvigor无法正常启动。检查build.gradle或hvigorfile.js文件，确保依赖配置正确。

  3. Hvigor版本兼容性：当前使用的Hvigor版本与鸿蒙Next版本不兼容，可能导致进程注册检查失败。更新Hvigor至最新版本，或回退至兼容版本。

  4. 环境配置问题：开发环境配置不完整或错误，可能导致Hvigor无法正常执行。检查环境变量、SDK路径等配置，确保符合要求。

  5. 进程冲突：系统中有其他进程占用了Hvigor所需的资源，导致其无法正常注册。检查系统进程，关闭可能冲突的进程。

以上是可能导致该问题的常见原因，具体解决方法需根据实际开发环境进一步分析。

回到顶部