Bug 303059 - Palapeli crashes (segmentation fault) while playing
Summary: Palapeli crashes (segmentation fault) while playing
Status: RESOLVED WORKSFORME
Alias: None
Product: palapeli
Classification: Applications
Component: general (show other bugs)
Version: 1.2
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Stefan Majewsky
URL:
Keywords:
: 303529 306931 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-07-05 12:09 UTC by Christian Deligant
Modified: 2018-11-07 06:23 UTC (History)
6 users (show)

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


Attachments
New crash information added by DrKonqi (5.24 KB, text/plain)
2013-06-08 23:08 UTC, Martin Walch
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Deligant 2012-07-05 12:09:25 UTC
Application: palapeli (1.2)
KDE Platform Version: 4.8.4 (4.8.4)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-26-generic x86_64
Distribution: Ubuntu 12.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:

The pieces were ordered and I was checking one block of already assembled pieces against all the ordered pieces moving downwards.

The crash can be reproduced some of the time.

-- Backtrace:
Application: Palapeli (palapeli), signal: Bus error
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa8e220a780 (LWP 32000))]

Thread 2 (Thread 0x7fa8d0b54700 (LWP 32001)):
#0  0x00007fa8dba92320 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007fa8dba92599 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fa8dba56c36 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fa8dba570a0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fa8dba57164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007fa8e08a9426 in QEventDispatcherGlib::processEvents (this=0x7fa8cc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x00007fa8e0878c82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#7  0x00007fa8e0878ed7 in QEventLoop::exec (this=0x7fa8d0b53dd0, flags=...) at kernel/qeventloop.cpp:204
#8  0x00007fa8e0777fa7 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#9  0x00007fa8e08589ff in QInotifyFileSystemWatcherEngine::run (this=0x1c51570) at io/qfilesystemwatcher_inotify.cpp:248
#10 0x00007fa8e077afcb in QThreadPrivate::start (arg=0x1c51570) at thread/qthread_unix.cpp:298
#11 0x00007fa8dc31be9a in start_thread (arg=0x7fa8d0b54700) at pthread_create.c:308
#12 0x00007fa8df16c4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#13 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fa8e220a780 (LWP 32000)):
[KCrash Handler]
#6  QGraphicsPixmapItem::shape (this=0x7fff39e07560) at graphicsview/qgraphicsitem.cpp:9715
#7  0x00007fa8e01d8406 in QGraphicsItem::setPos (this=0x4c743f0, pos=...) at graphicsview/qgraphicsitem.cpp:3729
#8  0x0000000000432178 in Palapeli::MovePieceInteractor::continueInteraction (this=0x1c39fc0, event=...) at ../../../palapeli/src/engine/interactors.cpp:102
#9  0x00000000004334df in Palapeli::InteractorManager::handleEventCommon (this=<optimized out>, pEvent=..., interactorData=..., unhandledButtons=...) at ../../../palapeli/src/engine/interactormanager.cpp:140
#10 0x0000000000433b5b in Palapeli::InteractorManager::handleEvent (this=0x1c46720, event=0x7fff39e08130) at ../../../palapeli/src/engine/interactormanager.cpp:106
#11 0x0000000000445d95 in Palapeli::View::mouseMoveEvent (this=0x1c590e0, event=0x7fff39e08130) at ../../../palapeli/src/engine/view.cpp:95
#12 0x00007fa8dfc4d178 in QWidget::event (this=0x1c590e0, event=0x7fff39e08130) at kernel/qwidget.cpp:8347
#13 0x00007fa8e000d3b6 in QFrame::event (this=0x1c590e0, e=0x7fff39e08130) at widgets/qframe.cpp:557
#14 0x00007fa8e0237b2b in QGraphicsView::viewportEvent (this=0x1c590e0, event=0x7fff39e08130) at graphicsview/qgraphicsview.cpp:2866
#15 0x00007fa8e087a028 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=<optimized out>, receiver=0x1c3bd80, event=0x7fff39e08130) at kernel/qcoreapplication.cpp:986
#16 0x00007fa8dfbfc85f in notify_helper (e=0x7fff39e08130, receiver=0x1c3bd80, this=0x1a55980) at kernel/qapplication.cpp:4555
#17 QApplicationPrivate::notify_helper (this=0x1a55980, receiver=0x1c3bd80, e=0x7fff39e08130) at kernel/qapplication.cpp:4531
#18 0x00007fa8dfc020bf in QApplication::notify (this=<optimized out>, receiver=0x1c3bd80, e=0x7fff39e08130) at kernel/qapplication.cpp:4102
#19 0x00007fa8e15389e6 in KApplication::notify (this=0x7fff39e08e10, receiver=0x1c3bd80, event=0x7fff39e08130) at ../../kdeui/kernel/kapplication.cpp:311
#20 0x00007fa8e0879e9c in QCoreApplication::notifyInternal (this=0x7fff39e08e10, receiver=0x1c3bd80, event=0x7fff39e08130) at kernel/qcoreapplication.cpp:876
#21 0x00007fa8dfbfd862 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#22 QApplicationPrivate::sendMouseEvent (receiver=0x1c3bd80, event=0x7fff39e08130, alienWidget=0x1c3bd80, nativeWidget=0x1be93a0, buttonDown=0x1c3bd80, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3170
#23 0x00007fa8dfc7cbf5 in QETWidget::translateMouseEvent (this=0x1be93a0, event=<optimized out>) at kernel/qapplication_x11.cpp:4617
#24 0x00007fa8dfc7bbae in QApplication::x11ProcessEvent (this=0x7fff39e08e10, event=0x7fff39e08a00) at kernel/qapplication_x11.cpp:3732
#25 0x00007fa8dfca50d2 in x11EventSourceDispatch (s=0x1a56f60, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#26 0x00007fa8dba56d53 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x00007fa8dba570a0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x00007fa8dba57164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x00007fa8e08a93bf in QEventDispatcherGlib::processEvents (this=0x1a304b0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#30 0x00007fa8dfca4d5e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#31 0x00007fa8e0878c82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#32 0x00007fa8e0878ed7 in QEventLoop::exec (this=0x7fff39e08da0, flags=...) at kernel/qeventloop.cpp:204
#33 0x00007fa8e087df67 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#34 0x00000000004248cd in main (argc=1, argv=0x7fff39e09158) at ../../../palapeli/src/main.cpp:51

Reported using DrKonqi
Comment 1 Christoph Feck 2012-12-20 04:26:50 UTC
*** Bug 303529 has been marked as a duplicate of this bug. ***
Comment 2 Christoph Feck 2012-12-20 04:27:11 UTC
*** Bug 306931 has been marked as a duplicate of this bug. ***
Comment 3 Martin Walch 2013-06-08 23:08:32 UTC
Created attachment 80406 [details]
New crash information added by DrKonqi

palapeli (1.2) on KDE Platform 4.10.4 using Qt 4.8.4

Still present in KDE 4.10.4.

Does not seem to be specific to Ubuntu (the three existing reports are all against Ubuntu 12.04).

- What I was doing when the application crashed:
I moved a group of already assembled parts to a single matching piece. Accidentally I clicked on the group again immediately after releasing the mouse button (I guess less than 0.3 seconds pause) before the connection animation even had a chance to put the pieces together.

-- Backtrace (Reduced):
#6  operator== (p2=..., p1=...) at ../../include/QtCore/../../src/corelib/tools/qpoint.h:331
#7  QGraphicsItem::setPos (this=0x1d1a100, pos=...) at graphicsview/qgraphicsitem.cpp:3722
#8  0x0000000000436e0b in Palapeli::MovePieceInteractor::continueInteraction (this=0x1c85160, event=...) at /var/tmp/portage/kde-base/palapeli-4.10.4/work/palapeli-4.10.4/src/engine/interactors.cpp:102
#9  0x000000000043a13d in Palapeli::InteractorManager::handleEventCommon (this=<optimized out>, pEvent=..., interactorData=..., unhandledButtons=...) at /var/tmp/portage/kde-base/palapeli-4.10.4/work/palapeli-4.10.4/src/engine/interactormanager.cpp:140
#10 0x000000000043aa7e in Palapeli::InteractorManager::handleEvent (this=<optimized out>, event=<optimized out>) at /var/tmp/portage/kde-base/palapeli-4.10.4/work/palapeli-4.10.4/src/engine/interactormanager.cpp:106
Comment 4 Andrew Crouthamel 2018-10-31 04:10:47 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Christian Deligant 2018-10-31 08:24:37 UTC
It doesn't crash anymore, thank you!
Comment 6 Martin Walch 2018-10-31 10:44:44 UTC
I also can not reproduce this bug with Palapeli 2.1 (KDE Applications 18.04.3) any more.

I suggest closing this bug as fixed.
Comment 7 Andrew Crouthamel 2018-10-31 14:45:16 UTC
Thanks for the update!
Comment 8 Ian Wadham 2018-11-07 06:23:31 UTC
See my comment and references in https://bugs.kde.org/show_bug.cgi?id=312267#c5 which I believe is a related bug.