Seg fault on image.save() (still?) #158
Comments
@WilliamMayor does it still segfault even if you pass a file object to from wand.image import Image
with Image(filename='image.gif') as img:
img.modulate(
brightness=0.95,
hue=0.95,
saturation=0.95
)
with open('modulated.gif', 'wb') as f:
img.save(file=f) |
@dahlia Yes, the code I'm actually using calls the EDIT. I just realised that the original issue states that the seg fault occurs on |
any news on this issue? I can confirm the segfault for ImageMagick 6.8.8-9 and Wand 0.3.7 using mac osx 10.8.5. Tried with ImageMagick 6.7.x still got the same problem. |
@WilliamMayor Try out the latest version of 0.3-maintenance. $ pip install git+https://github.com/dahlia/wand.git@0.3-maintenance#egg=Wand |
The bug is fixed in 0.3.8, a just released latest version. |
After running
modulate()
on an image,save()
will cause asegmentation fault: 11
.OS: OS X 10.9
Python: 2.7.5
Wand: 0.3.5
This might be related to issue #150
Here's a Gist with a demo Python script that causes a seg fault on my machine: https://gist.github.com/WilliamMayor/7353425#file-seg_fault_demo-py
I've also attached the image I'm using (just in case).
The text was updated successfully, but these errors were encountered: