View Issue Details

IDProjectCategoryView StatusLast Update
0004506ScribusInternalpublic2008-01-14 23:10
Reporterhva Assigned Tojghali  
PrioritynormalSeveritycrashReproducibilityalways
Status closedResolutionduplicate 
Platformamd_64 and intel i386OSUbuntu LinuxOS Version6.06-6.10
Product Version1.3.3.4 
Summary0004506: high number of images leads to a Out of Memory error and crash, with whole system instability
DescriptionCreating a document containing lot of high-resolution images leads to a Out of Memory error and a crash due to Signal 0000011.
on a 1Gb RAM system aproximately 80-90 digital camera pictures (5 megapixel resolution) are enough to crash Scribus. Same situation on 1.2.x Scribus doen't give any problem and is managed quite well.
The effect has been reproduced in every version of 1.3.x serie, including 1.3.4.
only message i could have is:
Out of memory in kernal/qimage.cpp
When i try to use dbg the system becomes so unstable i have to reset it without producing a debug report.
Steps To Reproduce1- take for example scribalbum2.py script from wiki (http://wiki.scribus.net/index.php/Automatic_import_of_images:_Versions_not_requiring_Tkinter)
(i use my own version that puts 2 images on a page)
2- run the script and pick a directory containing at least 100-150 pictures (i used 2592x1944 pixel images)
3- wait until Scribus has loaded more or less 80 pictures (with 1Gb RAM)
4- crash or frozen system (cpu load 0, but no responsiveness)
Additional InformationA file created with 1.2.x without problem containing enough hi-res images, can't even be opened in 1.3.x serie Scribus.
TagsNo tags attached.
Patch

Relationships

duplicate of 0004890 closed do not load pictures that are not selected to be displayed to save memory => crash 
has duplicate 0005897 closedjghali Scribus crashes with an EXCEPTION_ACCESS_VIOLATION loading a document containing many mid-resolution images 
child of 0002438 acknowledged Metabug: Cases of extreme memory use 

Activities

jghali

2008-01-14 23:10

administrator   ~0018589

Duplicate of 0004890

Issue History

Date Modified Username Field Change
2006-11-09 16:00 hva New Issue
2006-11-09 16:21 mhanski Relationship added child of 0002438
2007-07-15 14:54 jghali Relationship added has duplicate 0005897
2008-01-14 23:04 jghali Relationship added related to 0004890
2008-01-14 23:10 jghali Relationship replaced duplicate of 0004890
2008-01-14 23:10 jghali Duplicate ID 0 => 4890
2008-01-14 23:10 jghali Status new => resolved
2008-01-14 23:10 jghali Resolution open => duplicate
2008-01-14 23:10 jghali Assigned To => jghali
2008-01-14 23:10 jghali Note Added: 0018589
2008-01-14 23:10 jghali Status resolved => closed