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.

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

Fix timer not stopped on abort #257

Merged
merged 1 commit into from
Jan 31, 2024

Conversation

Lithopsian
Copy link
Contributor

The DirReadQueue zero-second timer is not stopped when a read is aborted, which leads to 100% cpu usage and lockup of some gui actions. The timer is only stopped when a job completes normally and at that point the queue is empty.

The timer could just be stopped in clear(), but to catch any other cases now or in the future, stop the timer whenever the queue is empty at the time that the timer fires.

The DirReadQueue zero-second timer is not stopped when a read is aborted, which leads to 100% cpu usage and lockup of some gui actions.  The timer is only stopped when a job completes normally and at that point the queue is empty.

The timer could just be stopped in clear(), but to catch any other cases now or in the future, stop the timer whenever the queue is empty at the time that the timer fires.
Copy link
Owner

@shundhammer shundhammer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thank you!

@shundhammer shundhammer merged commit 6328d7f into shundhammer:master Jan 31, 2024
@Lithopsian Lithopsian deleted the DirReadJobQueue-timer branch January 31, 2024 16:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants