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
Removing wrong call to cleanup_terminated_locked #2952
Conversation
The code removed was accidently added and shouldn't have been there in the first place
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
else if ((scheduler.get_scheduler_mode() & policies::fast_idle_mode) || | ||
idle_loop_count > params.max_idle_loop_count_ || may_exit) | ||
else if (((scheduler.get_scheduler_mode() & policies::fast_idle_mode) || | ||
(idle_loop_count > params.max_idle_loop_count_)) || may_exit) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The outer pair of parenthesis is superfluous.
thread_init_data background_init( | ||
[&, background_running](thread_state_ex_enum) -> thread_result_type | ||
[&idle_loop_count, bg_callback, background_running](thread_state_ex_enum) -> thread_result_type |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Line is too long.
This fixes the hangs we recently encountered
36544eb
to
10d0dd1
Compare
Superseded by #2962. |
The code removed was accidently added and shouldn't have been there in the
first place