Bugs item #984037, was opened at 2004-07-02 20:57
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428680&aid=984037&group_id=40696

Category: Behaviour
Group: CVS
Status: Open
Resolution: None
Priority: 5
Submitted By: Steven Wong (glutinous)
Assigned to: Nobody/Anonymous (nobody)
Summary: Imagemagick 'display' segfault when opening large images

Initial Comment:
When opening a 2000x2000 JPEG image with Imagemagick's
'display' tool, the following assert fails:

Blackbox::process_event(): MapRequest for 0x800014
BlackboxWindow::BlackboxWindow(): creating 0x800014
ImageMagick: too_high_and_wide.jpg -- assumed:
(-2147483648, 2147483644), real: >(0, -4)
blackbox: Window.cc:1648: void BlackboxWindow::show():
Assertion `client.rect.le>ft() == real_x &&
client.rect.top() == real_y' failed.
blackbox: managing screen 0 using TrueColor visual
0x20, depth 24
./run: line 17: 11451 Aborted                
blackbox/bin/blackbox
Shutting down Xnest server...
X connection to :1.0 broken (explicit kill or server
shutdown).

The command I am using to open the image is:

    display too_wide_and_high.jpg

Blackbox can handle opening 2000x10 and 10x2000 images,
though.

My desktop resolution is 1024x768. So I am guessing the
problem will only occur for windows larger than the
desktop resolution.

Other image viewers, such as 'qiv', work fine, so this
is an Imagemagick-specific problem.

I am running Debian Linux (Testing release), with the
latest Blackbox CVS, and Imagemagick package version
5:5.5.7.9-1.1. This package is based on Imagemagick
v5.5.7.9, as far as I know.

Attached is a log of debug messages from a session
leading up to the bug.

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428680&aid=984037&group_id=40696

-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
List archives:  http://asgardsrealm.net/lurker/splash/index.html
Trouble? Contact [EMAIL PROTECTED]

Reply via email to