Bug 315724 - kpat crashes playing spider (difficult mode) just moving mouse I think
Summary: kpat crashes playing spider (difficult mode) just moving mouse I think
Status: RESOLVED WORKSFORME
Alias: None
Product: kpat
Classification: Applications
Component: general (show other bugs)
Version: 3.6
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Stephan Kulow
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-24 17:42 UTC by Gregg
Modified: 2018-11-29 09:44 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gregg 2013-02-24 17:42:02 UTC
Application: kpat (3.6)
KDE Platform Version: 4.8.5 (4.8.5) "release 2"
Qt Version: 4.8.1
Operating System: Linux 3.4.28-2.20-default i686
Distribution: "openSUSE 12.2 (i586)"

-- Information about the crash:
- What I was doing when the application crashed:
Playing spider I think just moving the mouse -
system has 2G memory, had thunderbird, libreoffice(spreadsheet), knemo open
System does lock up twice a month seemingly on mouse movement

-- Backtrace:
Application: KPatience (kpat), signal: Segmentation fault
Using host libthread_db library "/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0xb48a9740 (LWP 4982))]

Thread 2 (Thread 0xb2552b40 (LWP 5241)):
[KCrash Handler]
#6  0xb5b68abd in __memcmp_ia32 () from /lib/libc.so.6
#7  0x0807bb13 in MemoryManager::insert_node (this=0x8c42960, n=0xb181e618, d=188, tree=0xb0ce3370, node=0xb25521cc) at /usr/src/debug/kdegames-4.8.5/kpat/patsolve/memory.cpp:54
#8  0x0807cb84 in Solver::insert (this=this@entry=0x8d5a5e0, cluster=cluster@entry=0xb25521c8, d=188, node=node@entry=0xb25521cc) at /usr/src/debug/kdegames-4.8.5/kpat/patsolve/patsolve.cpp:1054
#9  0x0807cc0c in Solver::new_position (this=this@entry=0x8d5a5e0, parent=parent@entry=0xb0886218, m=m@entry=0xb08cca28) at /usr/src/debug/kdegames-4.8.5/kpat/patsolve/patsolve.cpp:1079
#10 0x0807d052 in Solver::solve (this=this@entry=0x8d5a5e0, parent=parent@entry=0xb0886218) at /usr/src/debug/kdegames-4.8.5/kpat/patsolve/patsolve.cpp:741
#11 0x0807d2f2 in Solver::doit (this=this@entry=0x8d5a5e0) at /usr/src/debug/kdegames-4.8.5/kpat/patsolve/patsolve.cpp:666
#12 0x0807d95c in Solver::patsolve (this=0x8d5a5e0, _max_positions=-1, _debug=false) at /usr/src/debug/kdegames-4.8.5/kpat/patsolve/patsolve.cpp:960
#13 0x08068ad3 in SolverThread::run (this=0x8c31c28) at /usr/src/debug/kdegames-4.8.5/kpat/dealer.cpp:110
#14 0xb68fbd00 in ?? () from /usr/lib/libQtCore.so.4
#15 0xb5475e32 in start_thread () from /lib/libpthread.so.0
#16 0xb5bd77ee in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb48a9740 (LWP 4982)):
#0  0xb7746430 in __kernel_vsyscall ()
#1  0xb5bc61bb in read () from /lib/libc.so.6
#2  0xb51a0c7e in ?? () from /usr/lib/libglib-2.0.so.0
#3  0xb5161622 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#4  0xb5161a82 in ?? () from /usr/lib/libglib-2.0.so.0
#5  0xb5161c51 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#6  0xb6a3da81 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#7  0xb5fab1da in ?? () from /usr/lib/libQtGui.so.4
#8  0xb6a0aa3c in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#9  0xb6a0ad31 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#10 0xb6a0fcea in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#11 0xb5ef7934 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#12 0x0805cb2e in main (argc=3, argv=0xbfe3b054) at /usr/src/debug/kdegames-4.8.5/kpat/main.cpp:325

Possible duplicates by query: bug 193307.

Reported using DrKonqi
Comment 1 Andrew Crouthamel 2018-10-29 22:21:40 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 2 Bug Janitor Service 2018-11-13 14:41:47 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2018-11-29 09:44:26 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!