Skip to content
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

Seg fault on image.save() (still?) #158

Closed
WilliamMayor opened this issue Nov 7, 2013 · 5 comments
Closed

Seg fault on image.save() (still?) #158

WilliamMayor opened this issue Nov 7, 2013 · 5 comments
Labels
bug

Comments

@WilliamMayor
Copy link

@WilliamMayor WilliamMayor commented Nov 7, 2013

After running modulate() on an image, save() will cause a segmentation 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).

image

@dahlia
Copy link
Collaborator

@dahlia dahlia commented Dec 6, 2013

@WilliamMayor does it still segfault even if you pass a file object to file= keyword instead of filename=? E.g.

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)
@WilliamMayor
Copy link
Author

@WilliamMayor WilliamMayor commented Dec 6, 2013

@dahlia Yes, the code I'm actually using calls the Image(blob=blob) constructor but I've now tried file= and filename= and I still see the seg fault when the modulate method is called.

EDIT. I just realised that the original issue states that the seg fault occurs on save(). Looking at it now, it seems to happen on modulate(), not sure where I got my wires crossed on that one.

@fungt
Copy link
Contributor

@fungt fungt commented Mar 31, 2014

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.

fungt added a commit to fungt/wand that referenced this issue Mar 31, 2014
dahlia added a commit that referenced this issue Apr 2, 2014
@dahlia dahlia added the bug label Apr 2, 2014
@dahlia
Copy link
Collaborator

@dahlia dahlia commented Apr 2, 2014

@WilliamMayor Try out the latest version of 0.3-maintenance.

$ pip install git+https://github.com/dahlia/wand.git@0.3-maintenance#egg=Wand
@dahlia dahlia closed this in 3ed28c8 Jun 24, 2014
@dahlia
Copy link
Collaborator

@dahlia dahlia commented Aug 2, 2014

The bug is fixed in 0.3.8, a just released latest version.

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

Successfully merging a pull request may close this issue.

None yet
3 participants