Disk bloat dependencies

vvvv gamma bug
1

Hello!

I encounter a quite huge disk bloat and cannot really track it down yet what causes it.
The folder
C:\Program Files\vvvv\vvvv_gamma_7.0-win-x64\packs\dependencies\data\db
already has 320 GB.

We run a patch that evolved over the years, basics have been done in 2021.3.3 or such with latest updates to it in 7.0.
The patch uses vl.CEF for interface components, vl.Firmata (but most of it is gone already), Skia, VL.OpenCV with camera input, detections and conversions.

I need some conversions between texture to OpenCV, is it possible that they write to the disk?

Best, Andreas

2

See: Lib/data/db

3

the 2026 update on this situation:

as explained previously the large /db folder is a cache. you can avoid the folder filling up by avoiding usage of Strides FileTexture and FileModel nodes and using its non-caching variants TextureReader and ModelReader (experimental, available since 7.1) nodes instead.

also the folder can be savely deleted. here is how you do this:

for vvvv gamma 7.x and prior:

  • uninstall vvvv
  • manually delete the installation folder (e.g. C:\Program Files\vvvv\vvvv_gamma_7.0-win-x64) that is still left after the uninstall
  • reinstall vvvv

for vvvv gamma 8.0 (preview as of this writing)

  • close vvvv
  • delete the \data folder inside the vvvv installation folder (e.g. C:\Program Files\vvvv\vvvv_gamma_8.0-0028-g01fb53557a-win-x64\data)
  • restart vvvv
4

Thanks so much Björn and Joreg!

I was using FileTexture before and it had a reload pin that came in handy when reloading a camera image saved under the same filename over and over again. Same feature for TextureReader would be nice. I helped myself with a ManageProcess, maybe not the best way to do but it seems to work when reloading the image.

Maybe there is better way as well - I only used the save to SSD and reload because i could’t figure out a way to capture and rotate a webcam image for later use in OpenCV recognition and stride. Converting the CvImage to Image and then to (Stride) Texture restulted in unnecessary CPU use and trying to get conversion only when I needed them turned into crashes or other malfunctions. So maybe there is something I can do to only cache the image once to the Memory instead of writing to the SSD. Suggestions welcome. :slight_smile:

Would love to have our kids scan tool even more reliable on the long term. Thanks!