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

Crashing application will cause 'ghost window' #40

Open
AdaShoelace opened this issue Mar 18, 2020 · 1 comment
Open

Crashing application will cause 'ghost window' #40

AdaShoelace opened this issue Mar 18, 2020 · 1 comment
Labels
bug Something isn't working

Comments

@AdaShoelace
Copy link
Owner

In the event of a crashing application the window manager is not notified of the unmapping of the window and can therefor not delete the corresponding WindowWrapper.

This in turn leads to 'ghost windows' that can not be interacted with hence can not be deleted manually.
These ghost windows will cause the different layouts to behave as if they are still there, formatting existing windows in an unintended way and allocating screen space just to waste it.

@AdaShoelace AdaShoelace added the bug Something isn't working label Mar 18, 2020
@AdaShoelace AdaShoelace reopened this May 29, 2020
@AdaShoelace
Copy link
Owner Author

Reopening this issue due to reappearance of the bug.
It seems that some applications close top level windows (or hide) without sending an iccm-message telling us that the window is disappearing. This in term inhibits the clean-up of the corresponding WindowWrapper and gives faulty behaviour in tiling layouts. Desktop area containing no window will be allocated with no possibility to reclaim it.

In order to fix: identify under what circumstances this happens.
Can be reproduced with kazam.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant