Summary: | restarting game while dragging a piece leads to a crash | ||
---|---|---|---|
Product: | [Applications] palapeli | Reporter: | Martin Walch <walch.martin> |
Component: | general | Assignee: | Ian Wadham <iandw.au> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | Ch.Ehrlicher, iandw.au, kde-games-bugs, simonandric5 |
Priority: | NOR | Keywords: | drkonqi |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Martin Walch
2014-06-11 11:25:12 UTC
*** This bug has been marked as a duplicate of bug 312267 *** I can reproduce this bug in both KDE 4.12 and 4.13 versions of Palapeli, but not bug 312267. In both bugs, looking at the backtraces, it seems as though mouse-move events are coming in after the scene has changed and the piece that was being dragged has now gone somewhere else (i.e. it is no longer under the pointer). Created attachment 87326 [details]
New crash information added by DrKonqi
palapeli (2.0) on KDE Platform 4.13.2 using Qt 4.8.6
Palapeli 2.0, KDE 4.13, Apple OS X 10.7.5 Lion.
Same method of making Palapeli crash.
-- Backtrace (Reduced):
#4 0x0000000110f7d72d in QObject::disconnect ()
#5 0x000000010f80cf58 in Palapeli::MovePieceInteractor::stopInteraction (this=0x7fb470d22680, event=@0x0) at /kdedev/kde4.13/kdesrc/kde/kdegames/palapeli/src/engine/interactors.cpp:140
#6 0x000000010f80c21a in Palapeli::Interactor::setInactive () at /kdedev/kde4.13/kdesrc/kde/kdegames/palapeli/src/engine/interactor.h:122
#7 0x000000010f80c21a in Palapeli::Interactor::sendEvent (this=0x7fb470d22690, event=<value temporarily unavailable, due to optimizations>,
flags=<value temporarily unavailable, due to optimizations>) at /kdedev/kde4.13/kdesrc/kde/kdegames/palapeli/src/engine/interactor.cpp:132
#8 0x000000010f81012b in Palapeli::InteractorManager::handleEventCommon (this=<value temporarily unavailable, due to optimizations>, pEvent=@0x7fff6f3e2558, interactorData=@0x7fff6f3e2550,
unhandledButtons=@0x7fff6f3e2540) at /kdedev/kde4.13/kdesrc/kde/kdegames/palapeli/src/engine/interactormanager.cpp:140
Ian, so should we reopen this bug? (In reply to Christoph Feck from comment #4) > Ian, so should we reopen this bug? Yes, please. And please disentangle it from bug 312267. It is a different bug: different primary cause, similar symptoms. ATM I cannot work on these Palapeli piece-moving crashes, because I use Apple OS X on a MacBook Pro and have a more serious problem. KCrash and Dr Konqi will not run on Apple OS X. Comment 3 was one of my rare successes in getting the whole KDE 4 crash-reporting sequence to run. I have found the causes of one portability bug in KCrash and three in Dr Konqi, but there seem to be more problems in Dr K, to do with sockets, kdeinit4 and klauncher. The reason I have not reported these bugs on BKO is that apparently I am the only KDE developer with a KDE libs 4 test setup on Apple OS X and so nobody else could respond. I post the results of my work on repository playground/base/osx-patches, see https://projects.kde.org/projects/playground/base/osx-patches/repository/revisions/master/entry/README where they are available for use by MacPorts developers and the Frameworks developers, especially in Apple OS X CI. |