Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

RC High CPU usage when idle after reaching Ready state #1953

Closed
BobTB opened this issue Jul 2, 2016 · 4 comments
Closed

RC High CPU usage when idle after reaching Ready state #1953

BobTB opened this issue Jul 2, 2016 · 4 comments
Labels
performance stale Issue is no longer relevant, or was fixed and forgotten. If closed but still relevant, open a new. technical-debt This makes development harder or is leftover from a PullRequest. Needs to be adressed at some point.

Comments

@BobTB
Copy link

BobTB commented Jul 2, 2016 •
edited

The release candidate does a good job of finishing through to the Ready status, but it keeps consuming approx. 30% CPU continuously even if nothing is touched or running.Some Win32Exceptions in logs after it reaches Ready (attached).

image

image

log.txt
@BobTB BobTB changed the title High CPU usage when idle after reaching Ready state RC High CPU usage when idle after reaching Ready state Jul 2, 2016
@Hosch250
Copy link
Member

Hosch250 commented Jul 5, 2016

I'm guessing this is the point after Rubberduck is "technically" ready, but is A) running all the CanExecute's and disabling relevant commands, B) loading inspection results into the UI, and doing other things that have to way until immediately after a parse finishes.

@retailcoder
Copy link
Member

I can see the GroupingGrid controls being a problem: their data is loaded at least twice - once for the default/current grouping view, and another time for the other grouping view, which is loaded, but invisible.

@Vogel612
Copy link
Member

Is this still an issue for 2.0.8?

@Vogel612 Vogel612 added stale Issue is no longer relevant, or was fixed and forgotten. If closed but still relevant, open a new. technical-debt This makes development harder or is leftover from a PullRequest. Needs to be adressed at some point. labels Dec 7, 2017
@Vogel612
Copy link
Member

Vogel612 commented Dec 7, 2017

Haven't seen any issues like this in recent memory against my 20 module strong testproject... Issue also was last active half a year ago ...

@Vogel612 Vogel612 closed this as completed Dec 7, 2017
@SystemsModelling SystemsModelling mentioned this issue Jun 7, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
performance stale Issue is no longer relevant, or was fixed and forgotten. If closed but still relevant, open a new. technical-debt This makes development harder or is leftover from a PullRequest. Needs to be adressed at some point.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@retailcoder @Hosch250 @Vogel612 @BobTB