Describe the bug
When Windows Border feature of the extension enabled, and wl-copy or wl-paste is invoked, a memory leak occurs.
To Reproduce
Steps to reproduce the behavior:
- Enable Window Border
- Open a floating (!) terminal window and ensure you see the border around it
- Open a RAM usage monitoring software of your choice
- In the terminal, run
echo test | wl-copy a couple of times (copies "test" to the system clipboard)
- See the border flicker every time you run the command
- See RAM usage go up without ever going down
Screenshots
On a clean Ubuntu 25.10 live ISO in a VM (Ubuntu's tiling assistant disabled):
https://github.com/user-attachments/assets/71e29263-0022-4bb0-8420-87cae82bda41
On my Fedora 43 (the issue is much, much worse here):
https://github.com/user-attachments/assets/60638ba1-f921-461a-b21d-15e1fdaf43c5
Information (please complete the following):
- Tiling Shell version: 17.3
- GNOME version: 49.4
Additional context
To really hammer the bug home, run while true; do echo test | wl-copy; done and be ready to hit Ctrl+C :)
I experience this issue while using Neovim with :set clipboard+=unnamedplus. This makes any act of copying and pasting interact directly with the clipboard via wl-copy. After a while of using Neovim like that the memory fills up and a shell restart is required.
Describe the bug
When Windows Border feature of the extension enabled, and wl-copy or wl-paste is invoked, a memory leak occurs.
To Reproduce
Steps to reproduce the behavior:
echo test | wl-copya couple of times (copies "test" to the system clipboard)Screenshots
On a clean Ubuntu 25.10 live ISO in a VM (Ubuntu's tiling assistant disabled):
https://github.com/user-attachments/assets/71e29263-0022-4bb0-8420-87cae82bda41
On my Fedora 43 (the issue is much, much worse here):
https://github.com/user-attachments/assets/60638ba1-f921-461a-b21d-15e1fdaf43c5
Information (please complete the following):
Additional context
To really hammer the bug home, run
while true; do echo test | wl-copy; doneand be ready to hit Ctrl+C :)I experience this issue while using Neovim with
:set clipboard+=unnamedplus. This makes any act of copying and pasting interact directly with the clipboard via wl-copy. After a while of using Neovim like that the memory fills up and a shell restart is required.