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

debug logging can dead lock the X server #1173

Open
yshui opened this issue Jan 30, 2024 · 1 comment
Open

debug logging can dead lock the X server #1173

yshui opened this issue Jan 30, 2024 · 1 comment
Labels
bug priority:low Likely won't be done without some volunteers taking the task

Comments

@yshui
Copy link
Owner

yshui commented Jan 30, 2024

logging to the terminal can block, e.g. if the terminal emulator is not processing the outputs fast enough. and with debug logging enabled, picom logs in the server critical section (i.e. between XGrabServer and XUngrabServer). if picom got blocked there, it will in turn block the terminal emulator, because it will not be able to update its window when the server is grabbed. a dead lock.

this is low priority because debug logging is not usually enabled for day-to-day uses.
@yshui yshui added the priority:low Likely won't be done without some volunteers taking the task label Jan 30, 2024
@yshui
Copy link
Owner Author

yshui commented Jan 30, 2024

potential solution: make logging asynchronous with libev.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug priority:low Likely won't be done without some volunteers taking the task
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@yshui @absolutelynothelix