-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
High CPU usage; display nan% in memory; launch error report 3 times pop-up Dialog #1114
Comments
最后一个问题已解决, 解决方式: |
1 & 2 are limitations on Windows, afraid we can't do much better. Regarding 3, some github IP addresses are blocked for users in China, we need to support proxies - see #1050. Thanks for the report and the translation! |
(Just fixed the NaN% in memory thing) |
I'm afraid I'm still seeing the very high CPU usage on the latest windows version. |
@apLundell Could you share your machine specs and the version number that you've rolled back to? (can be found in the header of the Settings menu) Performance on Windows is difficult to get right, see this comment, but thread starvation (what you're experiencing with a lot of process spawns) should not be happening. |
Sure. I'm on
As for versions... I guess I was confused about what version I had. The version that works is reporting as "v3.0.0-pre" and if the file dates are to be trusted, It looks like I downloaded this on 5/5/2020. I guess that makes this a dev build? I don't remember why I installed a dev build. That's not something I would normally do. The versions that DON'T work for me, are the packaged windows releases. Like 2.2.7. Those work fine initially, but fifteen minutes later my system is unusable. So perhaps whatever my problem is, you've already fixed it. If so : Thanks! |
@apLundell Indeed, -pre are dev builds, but v2.2.7 should be better than a dev build from May last year. Could you try downloading one of the latest dev builds by going to https://github.com/GitSquared/edex-ui/actions/runs/938949307 and scrolling down to "Artifacts", to check that it is not a problem with the packaged versions? |
I just tried the v2.2.8-pre version and it worked great. Just to make sure I wasn't leading you on a goose-chase, I re-installed v2.2.7. It's still broken for me. It's not subtle. I just leave it running for five minutes and my computer is barely usable. Now I'm back on version v.2.2.8-pre and it's working great again. I'm going to leave it running overnight to make sure, but it really seems like whatever the problem is, it's not in this version. I hope this helps you track the problem down. |
Hmmm. Maybe some bad commit made its way into 2.2.7. I should make a release in the coming weeks either way. Thanks for trying it out & reporting back! |
1.CPU高占用
2.内存显示NaN%
3.初始开启程序报错
The text was updated successfully, but these errors were encountered: