Canop
viewing image in broot on kitty using filling too much ram
When i view images in broot on kitty terminal, it consistently adds the images into the ram, it never frees it even if i close broot. I will attach the video for your reference. It doesnt happen with fzf tho.
https://github.com/user-attachments/assets/f16941d7-11ee-4c8d-9414-cc5ed4aa5f24
I don't reproduce this.
Can you please launch broot with debug log enabled, view 2 images, then quit, and post the log here ?
Also please post your exact version of Kitty.
once I was casually browsing images in broot and it actually filled whole 8 gigs of ram and swap, and my system crashed
once I was casually browsing images in broot and it actually filled whole 8 gigs of ram and swap, and my system crashed
I fully understand it's a major bug. I just don't see ATM anything suspect in your log so I don't have explanation for now. I'll have to search for a way to diagnose what happens on your system. Does it happen if you use another compatible terminal, eg wezterm ?
https://github.com/user-attachments/assets/877b7ecb-6e44-4d32-8c22-230023e0365e
Its happening in wezterm also, can you try it with more than 15-20 high quality wallpapers and see if it reproduces?
can you try it with more than 15-20 high quality wallpapers and see if it reproduces?
I'm used to browse directories with thousands of files of several MB. To check it's not a recent bug I just passed over more than a dozen GB of images, with no problem and no decrease in available memory.
Besides such a bug would have been reported before if it was frequent.
Oh okay, thanks for making broot tho i use it regularly. One last thing, may i know which linux distro do you use 😀
@mukul1729 Do you by chance have the /tmp folder mounded in RAM ? If so, the last version 1.44.2 should help