View Issue Details

IDProjectCategoryView StatusLast Update
0013807ScribusOS-OS/2 & eCSpublic2016-12-29 23:43
Reportereilygre Assigned To 
PriorityhighSeveritymajorReproducibilityalways
Status newResolutionopen 
OSOS2OS VersioneCS 2.2 bII 
Product Version1.4.6 
Summary0013807: Display chaos or crash for "big" documents
DescriptionResent version is 1.4.5
A document created under an earlier version of Scribus can not be edited under any of my installed versions (1.4.0, 1.4.4, and 1.4.5) in OS2.
The document has 28 pages with a lot of pictures (ca. 100). Scribus normally crashes during loading after showing about 40-50 % loaded. Redirected output to textfile.
Sometimes the document is loaded, but the Scribus window is a mess - both the interior of the window and Scribus parts itself (menus etc.) Trying to capture the window using PMView gave nothing but a black pane. It is possible to repaint some part of the window by moving the cursor over it.
All other sla-documents (> 100) I have can be edited, but not this "big" one. For this one I use Win10 and Scr. 1.4.5
Steps To ReproduceJust run it again
Additional InformationAs I can't upload more the one file I here has a copy of another one of the redirected output files.

QImage: out of memory, returning null image
QImage: out of memory, returning null image
QImage: out of memory, returning null image
QImage: out of memory, returning null image
QImage: out of memory, returning null image
QImage: out of memory, returning null image
QImage: out of memory, returning null image
QImage: out of memory, returning null image
QImage: out of memory, returning null image
Application transferred too few scanlines
Application transferred too few scanlines
Application transferred too few scanlines
Application transferred too few scanlines
QImage: out of memory, returning null image
QImage: out of memory, returning null image
QImage: out of memory, returning null image
QImage: out of memory, returning null image
QImage: out of memory, returning null image
QImage: out of memory, returning null image
QImage: out of memory, returning null image
QImage: out of memory, returning null image
QImage: out of memory, returning null image
QImage: out of memory, returning null image
QImage: out of memory, returning null image
QImage: out of memory, returning null image
QImage: out of memory, returning null
Application transferred too few scanlines
Application transferred too few scanlines
Application transferred too few scanlines
Application transferred too few scanlines
Application transferred too few scanlines

Killed by SIGSEGV
pid=0x005e ppid=0x0027 tid=0x0001 slot=0x00b5 pri=0x0200 mc=0x0001 ps=0x0010
F:\DOWNLOAD\SCRIBUS\SCRIBUS-1.4.5-OS2-20151007\SCRIBUS-1.4.5\SCRIBUS.EXE
SCRIBUS 0:00533cb5
cs:eip=005b:1ccb3cb5 ss:esp=0053:0012a294 ebp=0012a78c
 ds=0053 es=0053 fs=150b gs=0000 efl=00210297
eax=fff2f2f2 ebx=00000000 ecx=0349c328 edx=00000000 edi=0012a400 esi=0d9280e0
Process dumping was disabled, use DUMPPROC / PROCDUMP to enable it.


NB. Info tool shows that the PC has 3000MB memory - should be enough

Parts of a much bigger file is displayed here, with some lines from the beginning of the file, some from the middle and some from the end:

Application transferred too few scanlines
Unable to load icon F:/Download/SCRIBUS/SCRIBUS-1.4.5-OS2-20151007/scribus-1.4.5/share/icons/16/page-doublesided.png: File not found
Unable to load icon F:/Download/SCRIBUS/SCRIBUS-1.4.5-OS2-20151007/scribus-1.4.5/share/icons/16/page-3fold.png: File not found
Unable to load icon F:/Download/SCRIBUS/SCRIBUS-1.4.5-OS2-20151007/scribus-1.4.5/share/icons/16/page-4fold.png: File not found
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::translate: Painter not active
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 2

-----------------
QPainter::scale: Painter not active
QPainter::translate: Painter not active
QPainter::setClipping: Painter not active, state will be reset by begin
QPainter::setClipRegion: Painter not active
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::translate: Painter not active
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::translate: Painter not active
QPainter::scale: Painter not active
QPainter::translate: Painter not active
QPainter::setClipping: Painter not active, state will be reset by begin
QPainter::setClipRegion: Painter not active
QPainter::begin: Paint device returned engine == 0, type: 2

------------------------
QPainter::save: Painter not active
QPainter::setBackgroundMode: Painter not active
QPainter::background: Painter not active
QPainter::setBrush: Painter not active
QPainter::setBrushOrigin: Painter not active
QPainter::setPen: Painter not active
QPainter::drawRects: Painter not active
QPainter::drawRects: Painter not active
QPainter::drawRects: Painter not active
QPainter::drawRects: Painter not active
QPainter::restore: Unbalanced save/restore



  
TagsNo tags attached.
PatchNo

Relationships

related to 0013111 closed Scribus reporting how much memory it is using (like in krita) 
child of 0002438 acknowledged Metabug: Cases of extreme memory use 

Activities

eilygre

2016-03-11 15:03

reporter  

feil3.txt (2,734 bytes)   
Could not open file "E:/HOME/DEFAULT/.scribus/downloads/scribus_spell_dicts.xml" 
Could not open file "E:/HOME/DEFAULT/.scribus/downloads/scribus_spell_dicts.xml" 
Application transferred too few scanlines
Application transferred too few scanlines
Application transferred too few scanlines
Application transferred too few scanlines
Application transferred too few scanlines
Application transferred too few scanlines
Application transferred too few scanlines
Application transferred too few scanlines
Application transferred too few scanlines
QImage: out of memory, returning null image
Application transferred too few scanlines
Application transferred too few scanlines
Application transferred too few scanlines
Application transferred too few scanlines
Application transferred too few scanlines
Application transferred too few scanlines
Application transferred too few scanlines
QImage: out of memory, returning null image
Application transferred too few scanlines
QImage: out of memory, returning null image
Application transferred too few scanlines
QImage: out of memory, returning null image
Application transferred too few scanlines
Application transferred too few scanlines
Application transferred too few scanlines
Application transferred too few scanlines
Application transferred too few scanlines
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::translate: Painter not active
QPainter::scale: Painter not active
QPainter::translate: Painter not active
QPainter::setClipping: Painter not active, state will be reset by begin
QPainter::setClipRegion: Painter not active
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::translate: Painter not active
QPainter::scale: Painter not active
QPainter::translate: Painter not active
QPainter::setClipping: Painter not active, state will be reset by begin
QPainter::setClipRegion: Painter not active
QPainter::save: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::pen: Painter not active
QPainter::translate: Painter not active
QPainter::drawRects: Painter not active
QPainter::setBrush: Painter not active
QPainter::setPen: Painter not active
QPainter::drawRects: Painter not active
QPainter::drawRects: Painter not active
QPainter::drawRects: Painter not active
QPainter::drawRects: Painter not active
QPainter::drawRects: Painter not active
QPainter::drawRects: Painter not active
QPainter::drawRects: Painter not active
QPainter::drawRects: Painter not active
QPainter::restore: Unbalanced save/restore
QThread::start: Failed to create thread (Not enough memory)
QThread::start: Failed to create thread (Not enough memory)
feil3.txt (2,734 bytes)   

cbradney

2016-03-11 19:19

administrator   ~0039133

Are you able to test this on a Windows, Linux or OSX machine? Some or all of it might relate to the OS2 build.

eilygre

2016-03-11 22:38

reporter   ~0039138

As I wrote in the description I have to edit this document in Windows 10. That works fine.

Kunda

2016-03-15 12:50

updater   ~0039175

@eilygre so this is not an issue on Windows 10 aka this is OS2 specific ?
Would you please share the original document with us so we can test it? If there is sensitive info in it we can label this ticket private

Kunda

2016-03-17 18:22

updater   ~0039225

In these cases it would be awesome if Scribus had a way to display used memory like in Krita 0013111

Issue History

Date Modified Username Field Change
2016-03-11 15:03 eilygre New Issue
2016-03-11 15:03 eilygre File Added: feil3.txt
2016-03-11 19:19 cbradney Note Added: 0039133
2016-03-11 22:38 eilygre Note Added: 0039138
2016-03-15 12:48 Kunda Relationship added child of 0002438
2016-03-15 12:50 Kunda Note Added: 0039175
2016-03-17 18:21 Kunda Relationship added related to 0013111
2016-03-17 18:22 Kunda Note Added: 0039225
2016-03-17 22:08 Kunda Summary Display caos or crash for "big" documents => Display chaos or crash for "big" documents
2016-12-29 23:43 plinnell Severity block => major