[Digikam-devel] [Bug 133567] crash when testing tags in digikam image editor (saveWithExiv2)

[Roger Larsson]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=133567         




------- Additional Comments From roger.larsson norran net  2006-09-06 23:30 -------
Uninitialized data is written.

==11943==
==11943== Syscall param write(buf) points to uninitialised byte(s)
==11943==    at 0x9091ECB: (within /lib64/libpthread-2.4.so)
==11943==    by 0x8CAD5BE: (within /usr/X11R6/lib64/libX11.so.6.2)
==11943==    by 0x8C91D2E: (within /usr/X11R6/lib64/libX11.so.6.2)
==11943==    by 0x8C6EF53: XCheckIfEvent (in /usr/X11R6/lib64/libX11.so.6.2)
==11943==    by 0x7A49117: QETWidget::translatePaintEvent(_XEvent const*) (in /usr/lib/qt3/lib64/libqt-mt.so.3.3.5)
==11943==    by 0x7A5473A: QApplication::x11ProcessEvent(_XEvent*) (in /usr/lib/qt3/lib64/libqt-mt.so.3.3.5)
==11943==    by 0x7A6322E: QEventLoop::processEvents(unsigned) (in /usr/lib/qt3/lib64/libqt-mt.so.3.3.5)
==11943==    by 0x7AC16A0: QEventLoop::enterLoop() (in /usr/lib/qt3/lib64/libqt-mt.so.3.3.5)
==11943==    by 0x7AC1549: QEventLoop::exec() (in /usr/lib/qt3/lib64/libqt-mt.so.3.3.5)
==11943==    by 0x402C33: main (in /opt/kde3/bin/digikam)
==11943==  Address 0xA454931 is 7,761 bytes inside a block of size 16,384 alloc'd
==11943==    at 0x4A1FB37: calloc (vg_replace_malloc.c:279)
==11943==    by 0x8C81FE6: XOpenDisplay (in /usr/X11R6/lib64/libX11.so.6.2)
==11943==    by 0x7A50D0E: qt_init_internal(int*, char**, _XDisplay*, unsigned long, unsigned long) (in /usr/lib/qt3/lib64/libqt-mt.so.3.3.5)
==11943==    by 0x7AB30B8: QApplication::construct(int&, char**, QApplication::Type) (in /usr/lib/qt3/lib64/libqt-mt.so.3.3.5)
==11943==    by 0x6F26313: KApplication::KApplication(bool, bool) (in /opt/kde3/lib64/libkdecore.so.4.2.0)
==11943==    by 0x402729: main (in /opt/kde3/bin/digikam)
digikam: /[...]/img_1084.jpg : JPEG file identified
digikam: Dirty: /
digikam: Exif color-space tag is sRGB. Using default sRGB ICC profile.
digikam: Exif Orientation: 1

* Moving forward to next image in Image Editor (no tag change) gives this:

digikam: /[...]/img_1085.jpg : JPEG file identified
digikam: Exif color-space tag is sRGB. Using default sRGB ICC profile.
digikam: Exif Orientation: 1

Clean while running!

But quitting shows some leaked memory:

==11943== ERROR SUMMARY: 528 errors from 29 contexts (suppressed: 58 from 2)
==11943== malloc/free: in use at exit: 845,536 bytes in 11,847 blocks.
==11943== malloc/free: 4,853,930 allocs, 4,842,083 frees, 902,706,257 bytes allocated.
==11943== For counts of detected errors, rerun with: -v
==11943== searching for pointers to 11,847 not-freed blocks.
==11943== checked 14,886,320 bytes.
==11943==
==11943== LEAK SUMMARY:
==11943==    definitely lost: 26,256 bytes in 376 blocks.
==11943==      possibly lost: 304 bytes in 1 blocks.
==11943==    still reachable: 818,976 bytes in 11,470 blocks.
==11943==         suppressed: 0 bytes in 0 blocks.

This new valgrind version did not have --tool=helgrind so I could not
see if this is a threading issue.