Broken Pipe Error Due to excessive spamming on Null Buffer attachment

[VimYoung]

Hyprland version: 0.50.0
OS and Kernel: 6.16.4-artix1-1

Pre-context: I am building a client for wayland from scratch. It is a WIP widget system. It has a hide window feature. Internally the feature attaches Null to layer which unmaps the buffer and commits on calling hide method and on calling back show_again method, the previous buffer is reattached.

Issue: On performance analysis, It was found that after calling hide and show a few times on a window. The event_queue is panicking with the following error.

o error: Broken pipe (os error 32)
Error trying to flush the wayland display: Broken pipe (os error 32)

thread 'main' panicked at /home/ramayen/Documents/projects/Spell/spell-framework/src/wayland_adapter.rs:442:18:
called `Result::unwrap()` on an `Err` value: OtherError(IoError(Os { code: 32, kind: BrokenPipe, message: "Broken pipe" }))

The internal logs suggest that as soon as null is attached and commited, Hyprland spams a excessive stream of configure calls to the layer. On calling show_again .The stream couldn't be processed at the same pace by the client and after a certain calls, the event_queue panics. Though I am not sure, there is a high possibility of it. I am open to corrections and suggestions.

Expected Behavior: The recall on configure should be manageable enough by the client side of wayland to process.

Possible Solutions: I don't know the internal working of server side of wayland but following approaches seems more apt for the situation.

1. Gaping the configure calls for avoid over spamming.
2. A rather weird solution, not calling config at all till a buffer is reattached on the window and commited. after which the first config call can be reinitiated.

Here is the following video showing the same. Config event is called is printed on call to configuration of layer. You can observe the conclusion mentioned in the clip.

screenrecord.mp4

[vaxerski]

a WAYLAND_DEBUG log and a test client would help

[VimYoung]

I am a bit busy so the work is stalled. I will provide a test case as soon as possible.