Bug 366482 - KMahjongg crashed after successfully completing game
Summary: KMahjongg crashed after successfully completing game
Status: RESOLVED DUPLICATE of bug 380114
Alias: None
Product: kmahjongg
Classification: Applications
Component: general (show other bugs)
Version: 0.9
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
Keywords: drkonqi
Depends on:
Reported: 2016-08-07 00:21 UTC by W Barker
Modified: 2017-05-29 23:15 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Note You need to log in before you can comment on or make changes to this bug.
Description W Barker 2016-08-07 00:21:23 UTC
Application: kmahjongg (0.9)

Qt Version: 5.6.1
Frameworks Version: 5.24.0
Operating System: Linux 4.6.4-301.fc24.x86_64 x86_64
Distribution: "Fedora release 24 (Twenty Four)"

-- Information about the crash:
- What I was doing when the application crashed:
As the title states, I had successfully completed a game. Previous iterations of the application, after successfully completing a game, would undo all moves until the original board was shown, then replay the game ... once.

This time, the completed game undid itself and restored the original board, then replayed the game, then undid itself AGAIN and restored the original board, then replayed the game, and started a THIRD time to undo the game ... at which point I closed the application, and the error was generated.

-- Backtrace:
Application: KMahjongg (kmahjongg), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
29	  return SYSCALL_CANCEL (wait4, pid, stat_loc, options, NULL);
[Current thread is 1 (Thread 0x7fecc1bc9900 (LWP 32211))]

Thread 2 (Thread 0x7fecacc91700 (LWP 32214)):
#0  0x00007fecd02c932d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007feccb0a9a46 in g_main_context_iterate (priority=<optimized out>, n_fds=1, fds=0x7feca8003020, timeout=<optimized out>, context=0x7feca8000990) at gmain.c:4135
#2  0x00007feccb0a9a46 in g_main_context_iterate (context=context@entry=0x7feca8000990, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3835
#3  0x00007feccb0a9b5c in g_main_context_iteration (context=0x7feca8000990, may_block=1) at gmain.c:3901
#4  0x00007fecd10cf24b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#5  0x00007fecd107e5ea in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#6  0x00007fecd0edd343 in QThread::exec() () at /lib64/libQt5Core.so.5
#7  0x00007fecd2ae7559 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5
#8  0x00007fecd0ee199a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5
#9  0x00007feccd4ee5ca in start_thread (arg=0x7fecacc91700) at pthread_create.c:333
#10 0x00007fecd02d4ead in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fecc1bc9900 (LWP 32211)):
[KCrash Handler]
#4  0x0000558f5ac4aab0 in  ()
#5  0x00007feca1b087e6 in NotifyByAudio::~NotifyByAudio() () at /lib64/libKF5Notifications.so.5
#6  0x00007feca1b08879 in NotifyByAudio::~NotifyByAudio() () at /lib64/libKF5Notifications.so.5
#7  0x00007fecd10ae4fc in QObjectPrivate::deleteChildren() () at /lib64/libQt5Core.so.5
#8  0x00007fecd10af5ff in QObject::~QObject() () at /lib64/libQt5Core.so.5
#9  0x00007feca1aeb6b9 in (anonymous namespace)::Q_QGS_s_self::innerFunction()::Holder::~Holder() () at /lib64/libKF5Notifications.so.5
#10 0x00007fecd020b1e8 in __run_exit_handlers (status=0, listp=0x7fecd058e5d8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#11 0x00007fecd020b235 in __GI_exit (status=<optimized out>) at exit.c:104
#12 0x00007fecd01f2738 in __libc_start_main (main=0x558f584b3ad0 <main>, argc=3, argv=0x7ffe1263a4d8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffe1263a4c8) at ../csu/libc-start.c:323
#13 0x0000558f584b4699 in _start ()

Reported using DrKonqi
Comment 1 Christoph Feck 2017-05-29 23:15:58 UTC

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