#763950 phototonic: Crashes on startup

Package:
phototonic
Source:
phototonic
Description:
image viewer and organizer
Submitter:
Kelly Clowers
Date:
2015-01-01 17:02:57 UTC
Severity:
important
#763950#5
Date:
2014-10-04 05:03:07 UTC
From:
To:
Dear Maintainer,

I saw phototonic show up today and thought I would try it.
However it does not start. When run from the command line I get this:

krc@ken:~$ phototonic
*** Error in `phototonic': free(): invalid pointer: 0x00007f90369005a0 ***
Aborted
krc@ken:~$

There is no dbg package currently or I'd try gdb.
I have not tried it on other systems.

#763950#10
Date:
2014-10-04 13:52:36 UTC
From:
To:
Hi Kelly,
 Does it remain the same after a full package update? You may try to
run it from gdb and see if you get more information. Do you have an
Intel or AMD CPU?
Does it crash if you supply a picture name as a parameter?

Cheers,
Laszlo/GCS

#763950#15
Date:
2014-10-04 18:06:03 UTC
From:
To:
I have an Intel Ivy Bridge. All packages it depends on where up to date,

I have now gone ahead and updated glib/gtk/pango (had been putting them
off since I didn't want to restart X before). So everything is
updated. Still the
same error. Also the same error when giving it an image as a parameter.

I tried gdb:

Reading symbols from phototonic...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/phototonic
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffec162700 (LWP 29615)]
*** Error in `/usr/bin/phototonic': free(): invalid pointer:
0x00007fffeeddd5a0 ***

Program received signal SIGABRT, Aborted.
0x00007ffff5248077 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
56    ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb)


Thanks,
Kelly

#763950#20
Date:
2014-10-05 12:14:25 UTC
From:
To:
 Meanwhile I realized phototonic has a bad memory usage pattern. At
least valgrind reports so. You may try it as well and post the output.
Simply try 'valgrind phototonic' or 'valgrind --leak-check=full -v
phototonic'.

Laszlo/GCS

#763950#25
Date:
2014-10-05 19:27:52 UTC
From:
To:
Yikes! Yeah, it is really bad it looks like.

krc@ken:~$ valgrind phototonic
==1403== Memcheck, a memory error detector
==1403== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==1403== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
==1403== Command: phototonic
==1403==
==1403== Invalid free() / delete / delete[] / realloc()
==1403==    at 0x4C29E90: free (vg_replace_malloc.c:473)
==1403==    by 0xE06670E: ??? (in
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so)
==1403==    by 0xE067F4F: ??? (in
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so)
==1403==    by 0x5CE86C3: ??? (in /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.3.2)
==1403==    by 0x5CEB0AC: QFontDatabase::findFont(int, QFontPrivate
const*, QFontDef const&, bool, bool) (in
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.3.2)
==1403==    by 0x5CEB9D0: QFontDatabase::load(QFontPrivate const*,
int) (in /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.3.2)
==1403==    by 0x5CC7208: QFontPrivate::engineForScript(int) const (in
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.3.2)
==1403==    by 0x5CE0552: QFontMetrics::height() const (in
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.3.2)
==1403==    by 0x5682A20: QHeaderView::minimumSectionSize() const (in
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.3.2)
==1403==    by 0x5682C89: QHeaderView::QHeaderView(Qt::Orientation,
QWidget*) (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.3.2)
==1403==    by 0x56A3E5C: ??? (in
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.3.2)
==1403==    by 0x44ED71: ??? (in /usr/bin/phototonic)
==1403==  Address 0xe0a45a0 is not stack'd, malloc'd or (recently) free'd
==1403==
==1403==
==1403== More than 10000000 total errors detected.  I'm not reporting any more.
==1403== Final error counts will be inaccurate.  Go fix your program!
==1403== Rerun with --error-limit=no to disable this cutoff.  Note
==1403== that errors may occur in your program without prior warning from
==1403== Valgrind, because errors are no longer being displayed.
==1403==

^C==1403==
==1403== HEAP SUMMARY:
==1403==     in use at exit: 664,333 bytes in 10,068 blocks
==1403==   total heap usage: 30,415 allocs, 1,749,980,603 frees,
3,691,062 bytes allocated
==1403==
==1403== LEAK SUMMARY:
==1403==    definitely lost: 2,564 bytes in 13 blocks
==1403==    indirectly lost: 7,348 bytes in 296 blocks
==1403==      possibly lost: 6,065 bytes in 102 blocks
==1403==    still reachable: 648,356 bytes in 9,657 blocks
==1403==         suppressed: 0 bytes in 0 blocks
==1403== Rerun with --leak-check=full to see details of leaked memory
==1403==
==1403== For counts of detected and suppressed errors, rerun with: -v
==1403== ERROR SUMMARY: 10000000 errors from 1 contexts (suppressed: 0 from 0)
Killed
krc@ken:~$


Kelly