Segmentation Fault (pygame parachute) caused by call to PythonMagick (minimal example attached)

[Ian]

pygame seems to be segfaulting after a call to pythonmagick. i tried running this through pdb, but it was unable to produce a backtrace.

here is the most basic code that produces the error on my machine:

####################################### start pygame_fail.py

import PythonMagick
import pygame

surface = pygame.Surface((128, 128), depth=8)
pygame.image.save(surface, "tmp.bmp")
img = PythonMagick.Image("tmp.bmp")

#THIS IS WHERE THE FAILURE HAPPENS
bb = img.boundingBox()

######################################## end

here is the failure (it fails in my ipython interpreter too):
###################################### start

$ ./pygame_fail.py
Fatal Python error: (pygame parachute) Segmentation Fault
Aborted

###################################### end

code versions on my machine:

kubuntu jaunty
2.6.28-17-generic #58-Ubuntu SMP
pygame 1.8.1release-0ubuntu2
pythonmagick 0.8-0ubuntu2.1
python 2.6.2

[Vincent Cheng (vincent-c)]

Does this still occur with the latest python-pygame package available in the repos (version 1.9.1release+dfsg-2)?

[Ian (ifreecarve)]

I have version 1.9.1release-0ubuntu1, and it looks like the segfault is gone.

$ python pygame_fail.py
Traceback (most recent call last):
  File "pygame_fail.py", line 9, in <module>
    bb = img.boundingBox()
RuntimeError: Magick: geometry does not contain image `tmp.bmp' @ warning/attribute.c/GetImageBoundingBox/239

[Launchpad Janitor (janitor)]

[Expired for pygame (Ubuntu) because there has been no activity for 60 days.]