Bug 276685

Summary:	After opening very big tif (790MB) closing krita lead to crash
Product:	[Applications] krita	Reporter:	Bruno Friedmann <bruno>
Component:	General	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	halla
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:

Description Bruno Friedmann 2011-06-28 12:55:23 UTC

Application: krita (2.4 Alpha 1)
KDE Platform Version: 4.6.4 (4.6.4)
Qt Version: 4.7.3
Operating System: Linux 2.6.39-2-desktop x86_64
Distribution: "openSUSE 12.1 Milestone 2 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed: I've opened a very very big tif file 790MB
I've test the rotate image function. 
Then I've no need about it, so file quit krita.
Then the crash occurs.

this can be reproduce (I've the data, and strace,valgrind tools installed) (but tif data are private ). If you are interrested, please give me the procedure you want

-- Backtrace:
Application: Krita (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#6  QWidget::releaseShortcut (this=0x137a560, id=-272) at kernel/qwidget.cpp:11164
#7  0x00007f43024ab523 in QLabelPrivate::clearContents (this=0x137b510) at widgets/qlabel.cpp:1365
#8  0x00007f43024ab819 in QLabel::~QLabel (this=<optimized out>, __in_chrg=<optimized out>) at widgets/qlabel.cpp:262
#9  0x00007f43024ab859 in QLabel::~QLabel (this=0x137a560, __in_chrg=<optimized out>) at widgets/qlabel.cpp:263
#10 0x00007f4302f0f925 in QObjectPrivate::deleteChildren (this=0x135e4a0) at kernel/qobject.cpp:1955
#11 0x00007f43021027d3 in QWidget::~QWidget (this=0x135e460, __in_chrg=<optimized out>) at kernel/qwidget.cpp:1631
#12 0x00007f4302102a79 in QWidget::~QWidget (this=0x135e460, __in_chrg=<optimized out>) at kernel/qwidget.cpp:1651
#13 0x00007f4302f0f925 in QObjectPrivate::deleteChildren (this=0x10ec7f0) at kernel/qobject.cpp:1955
#14 0x00007f43021027d3 in QWidget::~QWidget (this=0x11b5a90, __in_chrg=<optimized out>) at kernel/qwidget.cpp:1631
#15 0x00007f43024a8579 in QGroupBox::~QGroupBox (this=0x11b5a90, __in_chrg=<optimized out>) at widgets/qgroupbox.cpp:216
#16 0x00007f4302f0f925 in QObjectPrivate::deleteChildren (this=0x1157290) at kernel/qobject.cpp:1955
#17 0x00007f43021027d3 in QWidget::~QWidget (this=0x11907a0, __in_chrg=<optimized out>) at kernel/qwidget.cpp:1631
#18 0x00007f4302102a79 in QWidget::~QWidget (this=0x11907a0, __in_chrg=<optimized out>) at kernel/qwidget.cpp:1651
#19 0x00007f4302f0f925 in QObjectPrivate::deleteChildren (this=0x10328c0) at kernel/qobject.cpp:1955
#20 0x00007f43021027d3 in QWidget::~QWidget (this=0x1032880, __in_chrg=<optimized out>) at kernel/qwidget.cpp:1631
#21 0x00007f4302502cb9 in QStackedWidget::~QStackedWidget (this=0x1032880, __in_chrg=<optimized out>) at widgets/qstackedwidget.cpp:151
#22 0x00007f4302f0f925 in QObjectPrivate::deleteChildren (this=0x1032550) at kernel/qobject.cpp:1955
#23 0x00007f43021027d3 in QWidget::~QWidget (this=0x1032510, __in_chrg=<optimized out>) at kernel/qwidget.cpp:1631
#24 0x00007f4303bf6229 in KTabWidget::~KTabWidget (this=0x1032510, __in_chrg=<optimized out>) at /usr/src/debug/kdelibs-4.6.4/kdeui/widgets/ktabwidget.cpp:244
#25 0x00007f4302f0f925 in QObjectPrivate::deleteChildren (this=0x1031ac0) at kernel/qobject.cpp:1955
#26 0x00007f43021027d3 in QWidget::~QWidget (this=0x1031a80, __in_chrg=<optimized out>) at kernel/qwidget.cpp:1631
#27 0x00007f42d2c6f5b9 in ?? () from /usr/lib64/kde4/kritacolorselectorng.so
#28 0x00007f42e856f927 in KisPreferenceSetRegistry::~KisPreferenceSetRegistry() () from /usr/lib64/libkritaui.so.8
#29 0x00007f42e856fab9 in KisPreferenceSetRegistry::~KisPreferenceSetRegistry() () from /usr/lib64/libkritaui.so.8
#30 0x00007f4301895871 in __run_exit_handlers (status=0, listp=0x7f4301bdd4e8, run_list_atexit=true) at exit.c:78
#31 0x00007f43018958f5 in exit (status=<optimized out>) at exit.c:100
#32 0x0000000000408b06 in _start ()

This bug may be a duplicate of or related to bug 259262.

Possible duplicates by query: bug 259559, bug 259262.

Reported using DrKonqi

Comment 1 Halla Rempt 2011-06-29 08:08:29 UTC

Hi Bruno,

Thanks for your report. I don't think I really need the tiff file itself since I doubt that's the problem, just the dimensions and whether it was using a 16 bit/channel colorspace.

Currently we still seem to have a bit of a problem with getting the swapfile to work correctly if the image is really big -- we're trying to figure out where we are using too much memory and how to fix that. The good thing is that the more memory you have, the bigger the images you can open without problems :-).

Comment 2 Bruno Friedmann 2011-06-29 09:03:39 UTC

Tif information ( which is a geotif )
gdalinfo insane.tif

Size is 17452, 15820
Coordinate System is `'
Origin = (571991.500000000000000,257582.000000000000000)
Pixel Size = (0.250000000000000,-0.250000000000000)
Metadata:
  TIFFTAG_XRESOLUTION=1
  TIFFTAG_YRESOLUTION=1
  TIFFTAG_RESOLUTIONUNIT=1 (unitless)
Image Structure Metadata:
  INTERLEAVE=PIXEL
Corner Coordinates:
Upper Left  (  571991.500,  257582.000) 
Lower Left  (  571991.500,  253627.000) 
Upper Right (  576354.500,  257582.000) 
Lower Right (  576354.500,  253627.000) 
Center      (  574173.000,  255604.500) 
Band 1 Block=17452x1 Type=Byte, ColorInterp=Red
Band 2 Block=17452x1 Type=Byte, ColorInterp=Green
Band 3 Block=17452x1 Type=Byte, ColorInterp=Blue

Comment 3 Halla Rempt 2011-10-16 12:43:52 UTC


*** This bug has been marked as a duplicate of bug 259262 ***