Summary: | crash when testing tags in digikam image editor (saveWithExiv2) | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Roger Larsson <roger.larsson> |
Component: | Metadata-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | ahuggel, caulier.gilles |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 0.9.0 | |
Sentry Crash Report: |
Description
Roger Larsson
2006-09-04 22:20:46 UTC
Roger, Witch Exiv2 release you use. Here i connot reproduce the problem under Mandriva 2005-2006 and Suse 10.1 Here i'm using Exiv2 from svn (next 10.1 release). Gilles Caulier Andreas, Whats wrong with libc exactly ? There are a lots of crash report in libc. Any suggestions ? Gilles digikam et al. -> exiv2 -> STL -> libc The root cause for the memory corruption can be anywhere (or a 64bit issue, as this is on a 64bit system) Roger, can you please do this in Valgrind? Valgrind might be able to pinpoint the memory problem. Thanks, Andreas Roger, Look at end of HACKING file in digiKam trunk repository to see the notice about valgrind. Thanks in advance Gilles Paco, can you reproduce this crash under you 64 bits computer ? Gilles Valgrind build problem... missing libraries - tomorrow... 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. Thanks. So it doesn't crash when run in Valgrind and the issues Valgrind highlights are not related to Exiv2. Sounds good but doesn't help unfortunately. -ahu. Is these parts multithreaded? If so then running an older valgrind with --tool=helgrind [threading check] might give some additional info. Another crash about Exiv2 Gilles Roger, This could be a duplicate of bug #136855. Can you still recreate this? If so, please upgrade to the latest Exiv2 from SVN and check if it helps. Thanks! -ahu. Roger, This crash still reproductible using digiKam/DigikamImagePlugins 0.9.0-RC2 and Exiv2 0.12 ? Thanks in advance for your report. Gilles Caulier I updated and have been using a svn versions lately. Exiv2 0.11 DigikamImagePlugins v0.9.0-rc1 No problem that I can remember. I assume problem is fixed. |