wezterm icon indicating copy to clipboard operation
wezterm copied to clipboard

%APPDATA%/local/wezterm/wezterm-blob-lease-* directory taking up too much space (15 GB at one point)

Open ngomkhang134 opened this issue 1 year ago • 2 comments

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

Windows

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

No response

WezTerm version

wezterm 20241119-101432-4050072d

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

wezterm caching images too often when scrolling through image's previews in yazi (sxyazi/yazi). Yazi has a cache directory in C:\Users\Dell\AppData\Local\Temp\yazi but when i scroll through images, it also get cached into C:\Users\Dell\AppData\Local\wezterm\wezterm-blob-lease-itAw1SkV , the problem is ... it caches everytime i go to an image, even images it has cached before. And it also creates another file that has 3.6 MB as it does so, (the name format is "sha256-*"). So the folder's size grows really fast, at one point taking up 15 GB , before i delete it.

https://github.com/user-attachments/assets/81f3abbd-1368-4357-ab2d-a2b88b31a05a

To Reproduce

-install yazi via scoop details here -scroll through images and check C:\Users\Dell\AppData\Local\wezterm\wezterm-blob-lease-*\

Configuration

no config

Expected Behavior

C:\Users\Dell\AppData\Local\wezterm\wezterm-blob-lease-\ spawning new files (sha256-) as you go through images, spawn in pair (one for the image preview , one unknown file that has exactly 3.6 MB)

https://github.com/user-attachments/assets/11c12b83-5ce3-4cf6-b889-9ef0b9f538bd

Logs

No response

Anything else?

on linux , i think the cache directory is ~/.cache/wezterm/wezterm-blob-lease-*/

ngomkhang134 avatar Nov 21 '24 19:11 ngomkhang134

it's not just yazi, wezterm also cache files the same way with imgcat too (in the wezterm-blob-lease-* folder ) and it doesn't delete itselft after a restart. i've also filed the same issue in yazi, and the author says yazi doesn't instruct wezterm to make those caches, so it's probably on wezterm's end.

ngomkhang134 avatar Nov 22 '24 04:11 ngomkhang134

145GB here. I don't use yazi.

junkblocker avatar Jun 12 '25 23:06 junkblocker