-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation fault #156
Comments
Hello, I agree, I see a crash here with this test program: #!/usr/bin/env ruby
require 'vips'
l = Vips::Image.black 10, 10
l += 2
x = l.write_to_memory
y = l.write_to_memory I'll investigate. Thank you for the report! |
two writes in a row could trigger a crash in some circumstances, thanks @dirceupj see libvips/ruby-vips#156
I think I've found a nice fix -- would you be able to test HEAD of the 8.6 branch of libvips? |
@jcupitt Tested with HEAD of 8.6 (8.6.3). Works fine. Thank you.
I could properly execute the provided script in Issue first comment without segmentation fault occurrence. |
That's great, thanks! I'll push out 8.6.3 in a day or so with this fix. |
Hello,
I'm on MacOS. I'm getting segmentation fault after I use
.to_a
in a Vips::Image object. But it's not on a simple Vips::Image.In fact
.to_a
to a RGB Vips::Image works.But I get the segmentation fault when I do something like:
.rvm/gems/ruby-2.5.0/gems/ruby-vips-2.0.9/lib/vips/operation.rb:72: [BUG] Segmentation fault at 0x0000000000000000
ruby 2.5.0p0 (2017-12-25 revision 61468) [x86_64-darwin17]
-- Control frame information -----------------------------------------------
c:0009 p:---- s:0070 e:000069 CFUNC :vips_cache_operation_build
my libvips is 8.6.2 via homebrew
It does not matter if its a tiny of big image file.
I will not need to use
l.min
in production, but it is helping me to figure out something about my usage of libvips.The text was updated successfully, but these errors were encountered: