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: schedule output destruction on idle callback #1035

Merged
merged 1 commit into from
Feb 23, 2021

Conversation

alebastr
Copy link
Contributor

Defer destruction of bars for the output to the next iteration of the event loop to avoid deleting objects referenced by currently executed code.
Should fix some of the crashes on output disconnect. Could potentially cause a different kind of race conditions, but I haven't found anything that may happen in practice.

Testing: I've been running this patch for a week and attempting to reproduce the crash. Seems good so far.
@baloo, can you please try the patch and test if it fixes the issues in your setup?

Fixes #1019

@baloo
Copy link

baloo commented Feb 19, 2021

Deployed, I'll keep you posted! Thank you so much!

@baloo
Copy link

baloo commented Feb 23, 2021

I haven't seen a single crash in 4 days. I guess that fixed it.

Defer destruction of bars for the output to the next iteration of the
event loop to avoid deleting objects referenced by currently executed
code.
@alebastr alebastr marked this pull request as ready for review February 23, 2021 02:38
@Alexays
Copy link
Owner

Alexays commented Feb 23, 2021

Nice, thanks a lot!

@Alexays Alexays merged commit 1026100 into Alexays:master Feb 23, 2021
@alebastr alebastr deleted the deferred-output-removal branch February 23, 2021 16:08
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.

Crash on multiple monitors wake up
3 participants