HarmonyOS 鸿蒙Next DevEco偶现崩溃,一次崩溃后重启卡死,只能重新安装

HarmonyOS 鸿蒙Next DevEco偶现崩溃,一次崩溃后重启卡死,只能重新安装 版本是DevEco Studio 3.0.0.800

目前只发现崩溃是都会报错Hdc server port被使用的错误

hdc端口被占用整个软件都会十分卡顿或者崩溃吗?但是看报错次数有点多,一分钟十条吧

下面是stacktrace.txt的报错log

java.lang.Throwable: java.util.concurrent.TimeoutException
    at com.intellij.openapi.diagnostic.Logger.error(Logger.java:182)
    at com.huawei.harmony.run.deployment.DeviceSelectionProvider.getDebugBridge(DeviceSelectionProvider.java:235)
    at com.huawei.harmony.action.SelectDeviceAction.update(SelectDeviceAction.java:173)
    at com.intellij.openapi.actionSystem.ex.ActionUtil.lambda$performDumbAwareUpdate$0(ActionUtil.java:130)
    at com.intellij.openapi.actionSystem.ex.ActionUtil.performDumbAwareUpdate(ActionUtil.java:144)
    at com.intellij.openapi.actionSystem.impl.ActionUpdater.doUpdate(ActionUpdater.java:592)
    at com.intellij.openapi.actionSystem.impl.ActionUpdater.lambda$updateActionReal$7(ActionUpdater.java:132)
    at com.intellij.openapi.actionSystem.impl.ActionUpdater.lambda$callAction$9(ActionUpdater.java:187)
    at com.intellij.openapi.progress.ProgressManager.lambda$runProcess$0(ProgressManager.java:57)
    at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$2(CoreProgressManager.java:183)
    at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:705)
    at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:647)
    at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:63)
    at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:170)
    at com.intellij.openapi.progress.ProgressManager.runProcess(ProgressManager.java:57)
    at com.intellij.openapi.actionSystem.impl.ActionUpdater.lambda$callAction$10(ActionUpdater.java:185)
    at com.intellij.openapi.actionSystem.impl.ActionUpdateEdtExecutor.lambda$computeOnEdt$0(ActionUpdateEdtExecutor.java:45)
    at com.intellij.openapi.application.TransactionGuardImpl$2.run(TransactionGuardImpl.java:199)
    at com.intellij.openapi.application.impl.ApplicationImpl.runIntendedWriteActionOnCurrentThread(ApplicationImpl.java:789)
    at com.intellij.openapi.application.impl.ApplicationImpl.lambda$invokeLater$4(ApplicationImpl.java:350)
    at com.intellij.openapi.application.impl.FlushQueue.doRun(FlushQueue.java:84)
    at com.intellij.openapi.application.impl.FlushQueue.runNextEvent(FlushQueue.java:133)
    at com.intellij.openapi.application.impl.FlushQueue.flushNow(FlushQueue.java:46)
    at com.intellij.openapi.application.impl.FlushQueue$FlushNow.run(FlushQueue.java:189)
    at java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313)
    at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:776)
    at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:727)
    at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
    at java.base/java.security.AccessController.doPrivileged(Native Method)
    at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
    at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:746)
    at com.intellij.ide.IdeEventQueue.defaultDispatchEvent(IdeEventQueue.java:885)
    at com.intellij.ide.IdeEventQueue._dispatchEvent(IdeEventQueue.java:754)
    at com.intellij.ide.IdeEventQueue.lambda$dispatchEvent$6(IdeEventQueue.java:441)
    at com.intellij.openapi.progress.impl.CoreProgressManager.computePrioritized(CoreProgressManager.java:825)
    at com.intellij.ide.IdeEventQueue.lambda$dispatchEvent$7(IdeEventQueue.java:440)
    at com.intellij.openapi.application.impl.ApplicationImpl.runIntendedWriteActionOnCurrentThread(ApplicationImpl.java:789)
    at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:486)
    at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
    at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
    at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
    at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
    at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
    at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)

更多关于HarmonyOS 鸿蒙Next DevEco偶现崩溃,一次崩溃后重启卡死,只能重新安装的实战教程也可以访问 https://www.itying.com/category-93-b0.html

6 回复

这个可能就是端口号占用了,你修改个端口号试试

更多关于HarmonyOS 鸿蒙Next DevEco偶现崩溃,一次崩溃后重启卡死,只能重新安装的实战系列教程也可以访问 https://www.itying.com/category-93-b0.html


确定了,卡死问题就是这个报错引起的,我直接kill那个进程DevEco就好了,虽然现在报其他的错了,但是没有完全卡死能操作还是可以看下代码的。。。

这个问题还是要处理一下的,hdc端口被占用了也不至于整个应用卡死…这样的话每一次启动应用都是卡死的动都动不了…,

hdc端口占用确实会导致DevEco Studio卡顿和闪退,你修改一下端口号试试!

开发者您好,相关问题已经反馈给工作人员,稍后会再次回复您,感谢您对华为开发者论坛的支持。

针对“HarmonyOS 鸿蒙Next DevEco偶现崩溃,一次崩溃后重启卡死,只能重新安装”的问题,可能的原因及解决方案如下:

原因一:系统资源冲突或内存泄漏
在开发过程中,应用可能由于资源使用不当或内存管理问题导致崩溃。崩溃后,系统可能因资源未正确释放而处于不稳定状态,导致重启卡死。

解决方案:
检查应用代码,特别是内存管理部分,确保资源得到正确分配和释放。使用鸿蒙系统提供的内存检测工具进行问题定位。

原因二:系统bug或兼容性问题
鸿蒙系统本身可能存在bug,或者与开发环境存在兼容性问题,导致DevEco崩溃。

解决方案:
关注鸿蒙系统的更新日志和修复情况,确保使用的是最新版本的系统和开发环境。同时,尝试在不同的设备或模拟器上运行应用,以排除设备特定问题。

如果以上方法无法解决问题,可能需要更深入地分析崩溃日志和系统日志,以确定具体原因。此外,考虑到问题的复杂性,建议直接联系鸿蒙系统的官方技术支持团队进行进一步协助。

如果问题依旧没法解决请联系官网客服, 官网地址是 https://www.itying.com/category-93-b0.html

回到顶部