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.

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

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

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

Comments

Projects
None yet
4 participants
@BobTB

BobTB commented Jul 2, 2016

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 from High CPU usage when idle after reaching Ready state to RC High CPU usage when idle after reaching Ready state Jul 2, 2016

@Hosch250

This comment has been minimized.

Show comment
Hide comment
@Hosch250

Hosch250 Jul 5, 2016

Member

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.

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

This comment has been minimized.

Show comment
Hide comment
@retailcoder

retailcoder Jul 5, 2016

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.

Member

retailcoder commented Jul 5, 2016

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

This comment has been minimized.

Show comment
Hide comment
@Vogel612

Vogel612 Aug 20, 2016

Member

Is this still an issue for 2.0.8?

Member

Vogel612 commented Aug 20, 2016

Is this still an issue for 2.0.8?

@Vogel612

This comment has been minimized.

Show comment
Hide comment
@Vogel612

Vogel612 Dec 7, 2017

Member

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 ...

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 Dec 7, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment