[GEM-dev] [ pd-gem-Bugs-3521302 ] pix_write and pix_buffe crash when writing a file fail

[SourceForge.net]

Bugs item #3521302, was opened at 2012-04-25 02:27
Message generated for change (Comment added) made by zmoelnig
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3521302&group_id=64325

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Pixes (pix_ objects)
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Cyrille Henry (nusmuk)
Assigned to: Nobody/Anonymous (nobody)
Summary: pix_write and pix_buffe crash when writing a file fail

Initial Comment:
pix_write and pix_buffer crash when triing to write an image file in a non existant directory.
tested with GEM git from 2012 04 24 on linux

GEM: image saving support: jpeg magick tiff

tested with both jpeg and tiff file saving.

----------------------------------------------------------------------

>Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2012-04-27 06:29

Message:
that is weird.
i found a bug in imageJPEG that would indeed crash Gem whenever saving
failed (the mixed jpeg-62 and jpeg-80 system was only another problem that
triggered the abort; the fix in Gem's git  493e28ee0aef9cd should fix all
those problems)



if there is indeed a problem with imageMAGICK as well, please provide full
information about your installed ImageMagick as well as a backtrace

----------------------------------------------------------------------

Comment By: Cyrille Henry (nusmuk)
Date: 2012-04-27 06:23

Message:
hello,

i did have only libjpeg-62 install on my computer.

removing gem_imageJPEG.so and gem_imageJPEG.la file did not solve the
probleme.
The probleme was solved removing gem_imageMAGICK.*, but that disable png
image loading suport.


----------------------------------------------------------------------

Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2012-04-26 04:17

Message:
i could confirm the crash but noticed, that i have two different libjpeg
installations on my harddisk:
- libjpeg-62 headers in /usr/local/include (but not corresponding
libjpeg.so in /usr/local/lib - only a .a)
- libjpeg-80 headers in /usr/include AND libjpeg-80 libjpeg.so in
/usr/lib/i386-linux-gnu/

this resulted in imageJPEG being compiled against jpeg-62 headers, but
being linked with jpeg-80.
trying to write a file would abort (rather than crash) with a message
"Wrong JPEG library version: library is 80, caller expects 62"

once i removed the jpeg-62 headers and compiled Gem using the correct
jpeg-80 headers, everything works as expected (loading works as well, which
was not the case when using the mixed system (though it didn't abort))

could this be the same for you?

i haven't yet found a way to check the jpeg library version at runtime, in
order to prevent the abort.

----------------------------------------------------------------------

Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2012-04-26 03:57

Message:
afaict,  the imageJPEG backend causes the crash;
until the problem is fixed, you could try running Gem without imageJPEG
support (imageMAGICK will provide jpeg loading/saving anyhow)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3521302&group_id=64325