View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0011275||Scribus||General||public||2012-12-17 10:23||2012-12-17 13:26|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Platform||Acer Aspire M5201||OS||Windows 7||OS Version||Professional|
|Target Version||Fixed in Version|
|Description||I have recently been compiling a diary of a trip to Peru, which has run to about 30 pages and includes about 100 photos.|
Each picture is contained in a 'group' with a rectangular shape and a text frame for a caption.
It has suddenly 'corrupted' in some way, each picture, as it tries to open, gets an error message.
JPEG LIBRARY ERROR
Application transferred to few scanlines
and at one stage (after about 70 of the above error)
JPEG LIBRARY ERROR
Insufficient memory (case 4)
I am running Windows 7 Professional on an ACER Aspire M5201 with 4Gb of RAM memory
All the document is stored on a WD Elements USB Disc with 2TB of memory.
Can I recover my document somehow.
Any help will be appreciated I have spent many hours over the past 8 weeks, and as always when something like this happens I have not got a recent backup.
I do have a pdf version which has only about 4 hours work missing.
|Tags||No tags attached.|
||The severity has been assigned as minor, I would disagree with that as I have lost weeks of work and at present can only recover the text.|
The reason of these errors is due to your computer running out of memory.
To avoid memory related issues, we always recommend :
- to avoid using unnecessarily large images : a 100Mb image on a A4 pages is already too large, 30Mb is quite sufficient. And remember we always reason in term of uncompressed data : a 5Mb jpg file can translate to 100Mb of data once uncompressed.
- to split a document into multiple documents if it has lots of images, long text chains, or lots of pages
To continue working on your document, move temporarily images to another folder so you can open your document without loading images. Then split your document and move back images to their original place afterwards.
We recently made experimental 64bit builds of Scribus available. Those builds are able to use more than 2Gb of memory on Windows 64bit. If you use a 64bit edition of Windows, you can download and try the most recent build here :
I'm closing this issue as this is a duplicate of 0004520.
|2012-12-17 10:email@example.com||New Issue|
|2012-12-17 11:firstname.lastname@example.org||Note Added: 0029426|
|2012-12-17 13:26||jghali||Note Added: 0029431|
|2012-12-17 13:26||jghali||Relationship added||duplicate of 0004520|
|2012-12-17 13:26||jghali||Status||new => resolved|
|2012-12-17 13:26||jghali||Resolution||open => duplicate|
|2012-12-17 13:26||jghali||Assigned To||=> jghali|
|2012-12-17 13:26||jghali||Status||resolved => closed|