Skip to content

Conversation

ioquatix
Copy link
Member

I've been using this to help deal with memory usage issues.

@ioquatix ioquatix requested a review from jcupitt June 24, 2022 07:01
@Nakilon
Copy link
Contributor

Nakilon commented Jun 24, 2022

Hi. Just wondering. It is the thing that you've mentioned here? #67 (comment)
As I understand you said there it didn't help, only the GC.start did or something.

@ioquatix
Copy link
Member Author

Wow that was a while ago.

Well, I have not run the benchmarks again. That being said, in theory a close method makes sense. In practice, more work might be needed to make it practical/useful.

@jcupitt
Copy link
Member

jcupitt commented Jun 24, 2022

Hi, good idea, I've been meaning to add this.

Could we call it invalidate? That's the name we've used in the other libvips bindings.

close is rather close to post_close, the name we use for cleanup-on-finalize handlers.

@jdelStrother
Copy link

Doesn't this also need a Vips.attach_function :vips_image_invalidate_all, [:pointer], :void somewhere? Without it I get NoMethodError

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants