View Issue Details

IDProjectCategoryView StatusLast Update
0009542ScribusImport / Exportpublic2010-12-01 14:02
Reporteraturetta Assigned Tojghali  
Status closedResolutionduplicate 
Platform64bitOSWindowsOS VersionWindows 7 64bit
Product Version1.3.8 
Summary0009542: Crash when importing very large vector file
DescriptionWhen you try to import a very large vector file (several thousand objects), after using all the available memory in my PC, Scribus crashes with UNKNOWN EXCEPTION.
The original format doesn't make a difference, it happens with eps/ai/svg.

The file I attach, which exhibits the bug, is the result of tracing a bitmap with high accuracy, and contains little less than 20000 objects.

I understand it's big, but the software is almost ready for low-budget semi-professional working environment, it needs a better memory management.
Steps To Reproducebunzip the attached file, try to import in an empty scribus document.
Additional InformationThe file is exported from CorelDraw 10.
I'm working with Scribus 1.3.9 and 4GB RAM, memory usage is about 60% after opening Scribus, quickly rises to 89% just before the crash.

Here is the message on the console window:
Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.

Scribus Crash
Scribus crashes due to the following exception : UNKNOWN EXCEPTION

I can successfully open the file in InkScape 0.47 (although every redraw locks the interface for almost 5 seconds). Just for a reference, I tried to open the file with Illustrator 10 on a WindowsXP PC with 1GB Ram: less than a second, and negligible amount of memory used.... :-(
TagsNo tags attached.


duplicate of 0002221 closedfschmid scribus crash with signal 0000006 or complete freeze while trying to import complex svg files 



2010-12-01 12:01

reporter (1,603,233 bytes)


2010-12-01 12:04

reporter   ~0024951

I think this is linked to issue 0002221, but the resulting exception is different


2010-12-01 14:02

administrator   ~0024952

Same problem, the exception is only different because the system is different.

Issue History

Date Modified Username Field Change
2010-12-01 12:01 aturetta New Issue
2010-12-01 12:01 aturetta File Added:
2010-12-01 12:04 aturetta Note Added: 0024951
2010-12-01 14:02 jghali Note Added: 0024952
2010-12-01 14:02 jghali Relationship added duplicate of 0002221
2010-12-01 14:02 jghali Status new => resolved
2010-12-01 14:02 jghali Resolution open => duplicate
2010-12-01 14:02 jghali Assigned To => jghali
2010-12-01 14:02 jghali Status resolved => closed