[kmymoney] [Bug 391786] New: kmymoney git 5.0 crashes on exit, even if no file loaded

Jack bugzilla_noreply at kde.org
Mon Mar 12 22:32:18 UTC 2018


            Bug ID: 391786
           Summary: kmymoney git 5.0 crashes on exit, even if no file
           Product: kmymoney
           Version: 5.0.0
          Platform: Compiled Sources
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: kmymoney-devel at kde.org
          Reporter: ostroffjh at users.sourceforge.net
  Target Milestone: ---

I just compiled a new version (clean build dir) from git 5.0 branch.  Ran it as
"kmymoney -n" and got a repeatable crash on exit.

Initial load:

WebConnect: Try to connect to WebConnect server
WebConnect: Connect to server failed
WebConnect: Running in server mode
Plugins: checkprinting loaded
Plugins: csvexporter loaded
Plugins: csvimporter loaded
Plugins: gncimporter loaded
Plugins: icalendarexporter loaded
Plugins: ofximporter loaded
Plugins: qifexporter loaded
Plugins: qifimporter loaded
Plugins: reconciliation report loaded
Online plugins found 1

After exiting:

Plugins: checkprinting unloaded
Plugins: csvexporter unloaded
Plugins: csvimporter unloaded
Plugins: gncimporter unloaded
Plugins: icalendarexporter unloaded
Plugins: ofximporter unloaded
Plugins: qifexporter unloaded
Plugins: qifimporter unloaded
Plugins: reconciliation report unloaded
*** Error in `/home/jack/KDE/KMM/install50/bin/kmymoney': munmap_chunk():
invalid pointer: 0x00005650fb122f40 ***
======= Backtrace: =========
======= Memory map: ========
(I'll post the actual memory map if it would be helpful.

Oddly, if I load a file and then exit, I get a segmentation fault, but no
backtrace.  If I load a file, unload it, then exit, I get the crash.  Exit
either by File/Quit or click the "X" to close the window - same behavior.  If I
load a file, it seems to work and save fine.

If I run under gdb, doing bt after the crash gives:

(gdb) bt
#0  0x00007ffff0864ea0 in raise () from /lib64/libc.so.6
#1  0x00007ffff0866ac0 in abort () from /lib64/libc.so.6
#2  0x00007ffff08a7ce1 in ?? () from /lib64/libc.so.6
#3  0x00007ffff08af91b in ?? () from /lib64/libc.so.6
#4  0x00007ffff08b0e31 in ?? () from /lib64/libc.so.6
#5  0x00007ffff1603414 in QHashData::free_helper(void (*)(QHashData::Node*)) ()
from /usr/lib64/libQt5Core.so.5
#6  0x00007ffff6a8bb77 in QHash<eMyMoney::Transaction::Action,
QString>::freeData (this=0x7ffff6ca1b28
<CSVImporterCore::m_transactionConfName>, x=0x5555564b49e0)
    at /usr/include/qt5/QtCore/qhash.h:573
#7  0x00007ffff6a8c454 in QHash<eMyMoney::Transaction::Action, QString>::~QHash
(this=0x7ffff6ca1b28 <CSVImporterCore::m_transactionConfName>, 
    __in_chrg=<optimized out>) at /usr/include/qt5/QtCore/qhash.h:252
#8  0x00007ffff0868602 in __cxa_finalize () from /lib64/libc.so.6
#9  0x00007ffff6a63603 in ?? () from
#10 0x00007fffffffd5b0 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

I can't tell if there is enough data here to help, but I'll be glad to assist
with troubleshooting if possible.

You are receiving this mail because:
You are the assignee for the bug.

More information about the KMyMoney-devel mailing list