Bug 603818 - Converting image to Scipy array causes segfault
Summary: Converting image to Scipy array causes segfault
Alias: None
Product: Fedora
Classification: Fedora
Component: scipy   
(Show other bugs)
Version: 13
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Jef Spaleta
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-14 16:08 UTC by jpakkane
Modified: 2011-06-27 18:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-06-27 18:13:17 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Image that crashes Scipy (5.25 KB, image/png)
2010-06-14 16:08 UTC, jpakkane
no flags Details

Description jpakkane 2010-06-14 16:08:36 UTC
Created attachment 423887 [details]
Image that crashes Scipy

Attached is a simple file that segfaults Python when it is read with PIL and then converted to a Scipy array.

Here's a log of an interactive session that shows you how to replicate the bug.

localhost 18:28 0 > python
Python 2.6.4 (r264:75706, Apr  1 2010, 02:56:02) 
[GCC 4.4.3 20100226 (Red Hat 4.4.3-8)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import Image, scipy
>>> image = Image.open('scipy_crash.png')
>>> arr = scipy.asarray(image)
>>> arr
zsh: segmentation fault (core dumped)  python

Other images of the same type survive the last command. You can crash them by continuing with e.g. these commands:

from scipy import fftpack
x = fftpack.fft2(arr)

The probable reason for this crash is that the image is a PNG bitmap. When it is converted to a Scipy array the result is a Scipy array of booleans, not numbers. Somehow this causes a crash.

I have filed this against Scipy, but naturally the bug can also be in Numpy or PIL.

Comment 1 Bug Zapper 2011-06-02 10:53:14 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 2 Bug Zapper 2011-06-27 18:13:17 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.