| davidedmundson |
| KWin | |
| Frameworks |
If a client has not bound a certain output do not directly return
but try to deliver the buffer to other clients.
If none of them has requested it, send bufferReleased signal
immediately to let compositor know that the buffer should
be cleaned up.
Manually. Autotest planned.
| Automatic diff as part of commit; lint not applicable. |
| Automatic diff as part of commit; unit tests not applicable. |
| src/server/remote_access_interface.cpp | ||
|---|---|---|
| 216 | Would it be better to emit bufferReleased? Otherwise we're sometimes doing this deletion in the framework, sometimes in kwin | |
| src/server/remote_access_interface.cpp | ||
|---|---|---|
| 216 | True, is nicer. | |
Both versions solve issue I have and KWin no longer opens dozens of fds and abort when reaches the limit.
Add autotest. Needed larger refactoring to allow multiple clients with different outputs being bound.
At several places only one of two signal spies were waiting, what can lead to flickering tests.
Fixed this with an
if (spy.size() == 0) {
spy.wait();
}on the second spy. Is there a nicer solution?