wezterm imgcat does not deallocate image memory after closing instance

[d-hain]

What Operating System(s) are you seeing this problem on?

Linux X11

Which Wayland compositor or X11 Window manager(s) are you using?

i3 version 4.22 (2023-01-02)

WezTerm version

20240203-110809-5046fc22

Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?

Yes, and I updated the version box above to show the version of the nightly that I tried

Describe the bug

When I always have one instance of wezterm open and I open more and then execute wezterm imgcat image.png and close the new window again the memory of wezterm-gui always goes up.
It stops at around 1.3 GB for some reason.

To Reproduce

1. Open wezterm
2. Run a resource monitor like btop and look at wezterm-gui
3. Open another wezterm window
4. Run wezterm imgcat image.png (best seen with larger image files)
5. See the memory usage of wezterm-gui go up
6. Close the wezterm image with the image
7. Memory usage of wezterm-gui stays the same

Configuration

no config

Expected Behavior

Memory usage going down after closing the instance with the image

Logs

14:25:31.641 ERROR wezterm_mux_server_impl::local > writing pdu data buffer: Broken pipe (os error 32)
14:25:34.863 ERROR wezterm_mux_server_impl::local > writing pdu data buffer: Broken pipe (os error 32)
14:25:52.382 ERROR wezterm_mux_server_impl::local > writing pdu data buffer: Broken pipe (os error 32)
14:25:55.383 ERROR wezterm_mux_server_impl::local > writing pdu data buffer: Broken pipe (os error 32)
14:26:10.431 ERROR wezterm_mux_server_impl::local > writing pdu data buffer: Broken pipe (os error 32)
14:26:12.168 ERROR wezterm_mux_server_impl::local > writing pdu data buffer: Broken pipe (os error 32)
14:26:25.353 ERROR wezterm_mux_server_impl::local > writing pdu data buffer: Broken pipe (os error 32)

Anything else?

This could maybe be related to #2626 but that one is more about long term usage than specifically for imgcat