You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
today I encountered a strange bug while using the new VipsImage(File) constructor. When an image is loaded once, then the file is changed and then the image is loaded again using the file constructor, it seems that not the data from the file is loaded, but that libvips uses some cache which is not invalidated.
Steps to reproduce:
Read an image using the new VipsImage(File) constructor
Update the image file (I checked afterwards that the file was really changed)
Read the image again using the file constructor
Save the read image somewhere else
=> Then the saved image is equal to the old image.
The text was updated successfully, but these errors were encountered:
Hello,
I think it's because libvips cache the image either in memory or in disc temporary file:
In VIPS_ACCESS_RANDOM mode, small images are decompressed to memory and then processed from there. Large images are decompressed to temporary random-access files on disc and then processed from there.
Hi,
today I encountered a strange bug while using the
new VipsImage(File)
constructor. When an image is loaded once, then the file is changed and then the image is loaded again using the file constructor, it seems that not the data from the file is loaded, but thatlibvips
uses some cache which is not invalidated.Steps to reproduce:
new VipsImage(File)
constructor=> Then the saved image is equal to the old image.
The text was updated successfully, but these errors were encountered: