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

viewer consumes cpu after engine has closed #13225

Open
cyrush opened this issue Aug 3, 2021 · 0 comments
Open

viewer consumes cpu after engine has closed #13225

cyrush opened this issue Aug 3, 2021 · 0 comments
Labels
asc related to an asc funded project bug Something isn't working impact medium Productivity partially degraded (not easily mitigated bug) or improved (enhancement) likelihood medium Neither low nor high likelihood priority a priority ticket reviewed Issue has been reviewed and labeled by a developer

Comments

@cyrush
Copy link
Member

cyrush commented Aug 3, 2021

Describe the bug

I had an instance of visit open, batch allocation ran out, I left it open to resume later work.
Turns out the viewer was running at about 90% + CPU while waiting for me to return.
I received a nasty gram.

What should happen:

viewer shouldn't consume the cpu (especially if I haven't even issued a command to launch a new engine)
@cyrush cyrush added bug Something isn't working likelihood medium Neither low nor high likelihood impact medium Productivity partially degraded (not easily mitigated bug) or improved (enhancement) labels Aug 3, 2021
@brugger1 brugger1 added asc related to an asc funded project priority a priority ticket reviewed Issue has been reviewed and labeled by a developer labels Aug 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
asc related to an asc funded project bug Something isn't working impact medium Productivity partially degraded (not easily mitigated bug) or improved (enhancement) likelihood medium Neither low nor high likelihood priority a priority ticket reviewed Issue has been reviewed and labeled by a developer
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@brugger1 @cyrush