Application: kpat (3.6) Qt Version: 5.12.0 Frameworks Version: 5.54.0 Operating System: Linux 4.19.12-1-CHAKRA x86_64 Distribution: "Chakra" -- Information about the crash: - What I was doing when the application crashed: I can play as many games as I want, as far as I don't change the game. If I change the game a couple of times, it crashes. Always. The crash can be reproduced every time. -- Backtrace: Application: KPatience (kpat), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1ecb5e5800 (LWP 32743))] Thread 4 (Thread 0x7f1ea57f4700 (LWP 32756)): #0 0x00007f1ec267977d in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x00007f1ea65d69ab in ?? () from /usr/lib/dri/i965_dri.so #2 0x00007f1ea65d6717 in ?? () from /usr/lib/dri/i965_dri.so #3 0x00007f1ec2673523 in start_thread () from /usr/lib/libpthread.so.0 #4 0x00007f1ec6bf848f in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7f1eae7fc700 (LWP 32750)): #0 0x00007f1ec6bee00b in poll () from /usr/lib/libc.so.6 #1 0x00007f1ebe99257e in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x00007f1ebe99264c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x00007f1ec785c40b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #4 0x00007f1ec780695b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #5 0x00007f1ec7650bb6 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x00007f1ec38fac05 in ?? () from /usr/lib/libQt5DBus.so.5 #7 0x00007f1ec7651f02 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x00007f1ec2673523 in start_thread () from /usr/lib/libpthread.so.0 #9 0x00007f1ec6bf848f in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f1eb680d700 (LWP 32749)): #0 0x00007f1ec6bee00b in poll () from /usr/lib/libc.so.6 #1 0x00007f1ebcd3e922 in ?? () from /usr/lib/libxcb.so.1 #2 0x00007f1ebcd40727 in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x00007f1eb95f817a in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x00007f1ec7651f02 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x00007f1ec2673523 in start_thread () from /usr/lib/libpthread.so.0 #6 0x00007f1ec6bf848f in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f1ecb5e5800 (LWP 32743)): [KCrash Handler] #6 MemoryManager::new_from_block (this=0x5600be42c190, s=72) at /chakra/desktop/kpat/src/kpat-18.12.1/patsolve/memory.cpp:165 #7 0x00005600bd2314a7 in Solver<22ul>::pack_position (this=this@entry=0x5600be7496d0) at /chakra/desktop/kpat/src/kpat-18.12.1/patsolve/patsolve.cpp:209 #8 0x00005600bd23195e in Solver<22ul>::insert (this=this@entry=0x5600be7496d0, cluster=cluster@entry=0x7ffc7022627c, d=0, node=node@entry=0x7ffc70226280) at /chakra/desktop/kpat/src/kpat-18.12.1/patsolve/patsolve.cpp:873 #9 0x00005600bd231a4a in Solver<22ul>::new_position (this=this@entry=0x5600be7496d0, parent=parent@entry=0x0, m=m@entry=0x7ffc702262c0) at /chakra/desktop/kpat/src/kpat-18.12.1/patsolve/patsolve.cpp:906 #10 0x00005600bd2390e6 in Solver<22ul>::doit (this=0x5600be7496d0) at /chakra/desktop/kpat/src/kpat-18.12.1/patsolve/patsolve.cpp:487 #11 0x00005600bd239177 in Solver<22ul>::patsolve (this=0x5600be7496d0, _max_positions=<optimized out>) at /chakra/desktop/kpat/src/kpat-18.12.1/patsolve/patsolve.cpp:794 #12 0x00005600bd207f7f in DealerScene::isGameLost (this=0x5600be33ce10) at /chakra/desktop/kpat/src/kpat-18.12.1/dealer.cpp:1821 #13 0x00005600bd20f3b1 in DealerScene::takeState (this=this@entry=0x5600be33ce10) at /chakra/desktop/kpat/src/kpat-18.12.1/dealer.cpp:1314 #14 0x00005600bd21346c in DealerScene::animationDone (this=0x5600be33ce10) at /chakra/desktop/kpat/src/kpat-18.12.1/dealer.cpp:1530 #15 0x00007f1ec7831d90 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #16 0x00007f1ec7831d90 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #17 0x00007f1ec7831d90 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #18 0x00007f1ec783d997 in QTimer::timeout(QTimer::QPrivateSignal) () from /usr/lib/libQt5Core.so.5 #19 0x00007f1ec78324ab in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #20 0x00007f1ec8c95bd1 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #21 0x00007f1ec8c9d180 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #22 0x00007f1ec7807c89 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #23 0x00007f1ec785b803 in QTimerInfoList::activateTimers() () from /usr/lib/libQt5Core.so.5 #24 0x00007f1ec785c08c in ?? () from /usr/lib/libQt5Core.so.5 #25 0x00007f1ebe990abe in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #26 0x00007f1ebe992608 in ?? () from /usr/lib/libglib-2.0.so.0 #27 0x00007f1ebe99264c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #28 0x00007f1ec785c3f3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #29 0x00007f1ec780695b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #30 0x00007f1ec780eac2 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #31 0x00005600bd203f84 in main (argc=<optimized out>, argv=<optimized out>) at /chakra/desktop/kpat/src/kpat-18.12.1/main.cpp:339 Possible duplicates by query: bug 401369. Reported using DrKonqi
Can you try running it under valgrind? type valgrind kpat on the command line and then do what you do usually to make it crash and post the output here.
Cada cop que ho faig amb el valgrind em diu que la traça inversa no ha generat informació útil. Per si de cas ho he provat unes vuit o deu vegades. I entremig i ressetejat l'ordinador. I res. Every time I run it using valging it tells me the trace has generated no useful information. Just in case I've tried it maybe ten times, even reseting the computer. Nothing.
Can you make it crash one and tell us which games you changed from and to? i.e. you played gold, grandfather, klondike, etc and then it crashes. So we can try to reproduce the problem locally.
I play them in the order they are, skipping the seccond one, aces up. I usually play each one until I win one game. Then I go to the next one. And so one. Usually it crashes after the third or the fourth game. Maybe some times the fifth one. Time ago I could play them all.
Created attachment 118180 [details] New crash information added by DrKonqi kpat (3.6) using Qt 5.12.0 - What I was doing when the application crashed: I played spider, lost, played again, won. Played free cell, won. Played "El iaio" (granpa?). Crashed. -- Backtrace (Reduced): #5 MemoryManager::new_from_block (this=0x5596c9206440, s=72) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/memory.cpp:165 #6 0x00005596c70b84a7 in Solver<22ul>::pack_position (this=this@entry=0x5596cbdb7c10) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:209 #7 0x00005596c70b895e in Solver<22ul>::insert (this=this@entry=0x5596cbdb7c10, cluster=cluster@entry=0x7ffd05d90c3c, d=0, node=node@entry=0x7ffd05d90c40) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:873 #8 0x00005596c70b8a4a in Solver<22ul>::new_position (this=this@entry=0x5596cbdb7c10, parent=parent@entry=0x0, m=m@entry=0x7ffd05d90c80) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:906 #9 0x00005596c70c00e6 in Solver<22ul>::doit (this=0x5596cbdb7c10) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:487
Do you have the solver enabled?
Created attachment 118199 [details] New crash information added by DrKonqi kpat (3.6) using Qt 5.12.0 - What I was doing when the application crashed: This time I've disabled the solver (the other times it was on) and it has taken a little longer to crash. I've been able to win 5 games and it has crashed while playing Gypsy. -- Backtrace (Reduced): #5 MemoryManager::new_from_block (this=0x55adc44e8f00, s=64) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/memory.cpp:165 #6 0x000055adc3894277 in Solver<17ul>::pack_position (this=this@entry=0x55adc44e8180) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:209 #7 0x000055adc389472e in Solver<17ul>::insert (this=this@entry=0x55adc44e8180, cluster=cluster@entry=0x7ffcd2fe995c, d=0, node=node@entry=0x7ffcd2fe9960) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:873 #8 0x000055adc389481a in Solver<17ul>::new_position (this=this@entry=0x55adc44e8180, parent=parent@entry=0x0, m=m@entry=0x7ffcd2fe99a0) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:906 #9 0x000055adc389b4f6 in Solver<17ul>::doit (this=0x55adc44e8180) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:487
Created attachment 118206 [details] New crash information added by DrKonqi kpat (3.6) using Qt 5.12.0 - What I was doing when the application crashed: Played two games with solver on. On third games, on checking if solver was really on, it has crashed. -- Backtrace (Reduced): #5 MemoryManager::new_from_block (this=0x5613d69fe1b0, s=72) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/memory.cpp:165 #6 0x00005613d59ee4a7 in Solver<22ul>::pack_position (this=this@entry=0x5613d6e03490) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:209 #7 0x00005613d59ee95e in Solver<22ul>::insert (this=this@entry=0x5613d6e03490, cluster=cluster@entry=0x7ffe90967dfc, d=0, node=node@entry=0x7ffe90967e00) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:873 #8 0x00005613d59eea4a in Solver<22ul>::new_position (this=this@entry=0x5613d6e03490, parent=parent@entry=0x0, m=m@entry=0x7ffe90967e40) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:906 #9 0x00005613d59f60e6 in Solver<22ul>::doit (this=0x5613d6e03490) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:487
Created attachment 118209 [details] New crash information added by DrKonqi kpat (3.6) using Qt 5.12.0 - What I was doing when the application crashed: two games played, at the third one it has crashed.. -- Backtrace (Reduced): #5 MemoryManager::new_from_block (this=0x557a8ad4cdb0, s=72) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/memory.cpp:165 #6 0x0000557a889ce4a7 in Solver<22ul>::pack_position (this=this@entry=0x557a8b0fa170) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:209 #7 0x0000557a889ce95e in Solver<22ul>::insert (this=this@entry=0x557a8b0fa170, cluster=cluster@entry=0x7ffce83b1b7c, d=0, node=node@entry=0x7ffce83b1b80) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:873 #8 0x0000557a889cea4a in Solver<22ul>::new_position (this=this@entry=0x557a8b0fa170, parent=parent@entry=0x0, m=m@entry=0x7ffce83b1bc0) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:906 #9 0x0000557a889d60e6 in Solver<22ul>::doit (this=0x557a8b0fa170) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:487
I’m using Chakra as well, and I’m unable to reproduce this issue :| Version-wise, the only difference I see is that I’ve just upgraded to KF 5.55.0. Could you upgrade as well and try again? Víktor, have you used makepkg, ccr or similar to build a package from sources, or do you use only packages from the main Chakra repositories? If the latter, which repository are you using?
Not sure what you mean about upgrading. Everything in core that has "(kf5)" is version 5.55.0-1 About building packages from sources, I think the only one I use is the telegram one, tdesktop. The repositories I'm using are lib32, core, desktop and gtk.
When I said repositories, I meant mirrors, but to be honest it’s a long stretch. I can’t think of a good reason why it would crash for you and not for me. If you are really invested into getting this fixed, I guess the best steps to follow now would be to install the kpat-debug package (Chakra includes separate -debug packages for all KDE software, which should make tracebacks more useful), and see if you can get a more useful backtrace then. Bona sort!
Do mirrors matter? kpat version installed is 18.12.2-1 This is my current /etc/pacman.d/mirrorlist ----------------------------- # Chakra repository mirrorlist # The first not commented (no # at the beginning of the line) mirror is # used. Mirrors are used in order, starting from the top. Add a # at # the start of a line to disable a mirror. # Australia Server = http://mirror.aarnet.edu.au/pub/chakra/$repo/x86_64 # Brazil Server = http://chakra.c3sl.ufpr.br/$repo/x86_64 # China Server = http://mirrors.ustc.edu.cn/chakra/$repo/x86_64 Server = http://mirrors.tuna.tsinghua.edu.cn/chakra/$repo/x86_64 # Colombia Server = http://mirror.edatel.net.co/chakra/$repo/x86_64 # France Server = http://www-ftp.lip6.fr/pub/linux/distributions/chakra/$repo/x86_64 Server = http://ftp.ciril.fr/pub/linux/chakra/$repo/x86_64 Server = http://elgrande74.net/chakra/packages/$repo/x86_64 Server = https://mirrors.deogracia.xyz/chakra/packages/$repo/x86_64 # Germany Server = http://ftp.halifax.rwth-aachen.de/chakra/$repo/x86_64 Server = http://mirror.selfnet.de/chakra/$repo/x86_64 Server = http://mirror.wh-stuttgart.net/chakra/$repo/x86_64 Server = https://mirror.alpix.eu/chakra/$repo/x86_64 #Server = https://rsync.chakralinux.org/packages/$repo/x86_64 # Greece Server = http://ftp.cc.uoc.gr/mirrors/linux/chakra/$repo/x86_64 # Italy Server = http://chakra.mirror.garr.it/mirrors/chakra/$repo/x86_64 # Russia Server = http://mirror.yandex.ru/mirrors/chakra/$repo/x86_64 # Sweden Server = http://ftp.acc.umu.se/mirror/chakralinux.org/packages/$repo/x86_64 # Switzerland Server = https://mirror.puzzle.ch/chakralinux/$repo/x86_64 # Taiwan Server = http://free.nchc.org.tw/chakra/packages/$repo/x86_64 Server = http://ftp.yzu.edu.tw/Linux/chakra/$repo/x86_64 Server = http://mirror.ossplanet.net/chakra/packages/$repo/x86_64 Server = http://ftp.ubuntu-tw.org/mirror/chakra/packages/$repo/x86_64 Server = http://ftp.tku.edu.tw/Linux/Chakra/packages/$repo/x86_64 # United States Server = http://mirror.rit.edu/chakra/$repo/x86_64 Server = http://www.gtlib.gatech.edu/pub/chakra/packages/$repo/x86_64 ---------------------------------- So I guess I'm using the one in Australia. I have kpat-debug installed since Albert asked me to use valgrind, but running valgrind kpat gets me a message saying the trace is useless... :-(
You could try building kpat yourself in debug mode. It may be as easy as using https://code.chakralinux.org/chakra/packages/desktop/blob/master/kpat/PKGBUILD and changing RelWithDebInfo to Debug. If that does not make a difference, I am out of ideas.
Never mind that, your last traceback includes affected files and lines. I think that is as helpful as a traceback can get. It looks like memory corruption related to the solver, but my understanding is quite limited, so I might be wrong. As a last attempt to find a set of steps that I can reproduce, I suggest you start the game and try to find a way to reproduce the crash using specific game seeds (Joc → Nova má numerada…). So, start the app, start all your games with that menu option and write down which game and seed number you use, and let the solver play the game. Once you get a crash, try to repeat the same experience (restart the app, use the same sequence of games and seed numbers), and see if it crashes at the same point as before. If you can reproduce the crash reliably with such a sequence of steps, let us know the sequence that you followed (e.g. [[El iaio, 1], [El iaio, 2], [Golf, 1]]). Otherwise… it will be hard for someone to be able to fix the issue, albeit not impossible.
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!
It does really crash for him, but not for us, closing it is bad manners, but note that if no developer can reproduce it, it will most probably not be fixed
Created attachment 118779 [details] New crash information added by DrKonqi kpat (3.6) using Qt 5.12.1 - What I was doing when the application crashed: It crashed just on starting the third different game. -- Backtrace (Reduced): #6 MemoryManager::new_from_block (this=0x55cd02be3be0, s=72) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/memory.cpp:165 #7 0x000055cd01c964a7 in Solver<22ul>::pack_position (this=this@entry=0x55cd02fe7780) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:209 #8 0x000055cd01c9695e in Solver<22ul>::insert (this=this@entry=0x55cd02fe7780, cluster=cluster@entry=0x7ffee8d9865c, d=0, node=node@entry=0x7ffee8d98660) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:873 #9 0x000055cd01c96a4a in Solver<22ul>::new_position (this=this@entry=0x55cd02fe7780, parent=parent@entry=0x0, m=m@entry=0x7ffee8d986a0) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:906 #10 0x000055cd01c9e0e6 in Solver<22ul>::doit (this=0x55cd02fe7780) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:487
Created attachment 118800 [details] New crash information added by DrKonqi kpat (3.6) using Qt 5.12.1 - What I was doing when the application crashed: It crashed just at the begining of the third different game. -- Backtrace (Reduced): #6 MemoryManager::new_from_block (this=0x5599a7487a00, s=72) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/memory.cpp:165 #7 0x00005599a57a54a7 in Solver<22ul>::pack_position (this=this@entry=0x5599a9dd4390) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:209 #8 0x00005599a57a595e in Solver<22ul>::insert (this=this@entry=0x5599a9dd4390, cluster=cluster@entry=0x7ffc79ffba1c, d=0, node=node@entry=0x7ffc79ffba20) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:873 #9 0x00005599a57a5a4a in Solver<22ul>::new_position (this=this@entry=0x5599a9dd4390, parent=parent@entry=0x0, m=m@entry=0x7ffc79ffba60) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:906 #10 0x00005599a57ad0e6 in Solver<22ul>::doit (this=0x5599a9dd4390) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:487
Created attachment 118811 [details] New crash information added by DrKonqi kpat (3.6) using Qt 5.12.1 - What I was doing when the application crashed: It crashed just on opening the third different game, "el iaio" (grandad?). -- Backtrace (Reduced): #6 MemoryManager::new_from_block (this=0x55ad95c92090, s=72) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/memory.cpp:165 #7 0x000055ad953464a7 in Solver<22ul>::pack_position (this=this@entry=0x55ad96096c80) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:209 #8 0x000055ad9534695e in Solver<22ul>::insert (this=this@entry=0x55ad96096c80, cluster=cluster@entry=0x7ffe298e297c, d=0, node=node@entry=0x7ffe298e2980) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:873 #9 0x000055ad95346a4a in Solver<22ul>::new_position (this=this@entry=0x55ad96096c80, parent=parent@entry=0x0, m=m@entry=0x7ffe298e29c0) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:906 #10 0x000055ad9534e0e6 in Solver<22ul>::doit (this=0x55ad96096c80) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:487
No need for further tracebacks or steps, Víktor. However, if you ever manage to reproduce the issue on a different computer, or find someone else that can reproduce the issue, please do let us know.
Created attachment 118897 [details] New crash information added by DrKonqi kpat (3.6) using Qt 5.12.1 - What I was doing when the application crashed: It has crashed when starting the third different game in a row. It shows the cards but I have no time to even click on anything before it crashes. -- Backtrace (Reduced): #6 MemoryManager::new_from_block (this=0x561d43a018a0, s=48) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/memory.cpp:165 #7 0x0000561d4248b917 in Solver<9ul>::pack_position (this=this@entry=0x561d437181c0) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:209 #8 0x0000561d4248bdce in Solver<9ul>::insert (this=this@entry=0x561d437181c0, cluster=cluster@entry=0x7ffefa2b54bc, d=0, node=node@entry=0x7ffefa2b54c0) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:873 #9 0x0000561d4248beba in Solver<9ul>::new_position (this=this@entry=0x561d437181c0, parent=parent@entry=0x0, m=m@entry=0x7ffefa2b5500) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:906 #10 0x0000561d424948c6 in Solver<9ul>::doit (this=0x561d437181c0) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:487
Created attachment 118951 [details] New crash information added by DrKonqi kpat (3.6) using Qt 5.12.1 - What I was doing when the application crashed: It has crashed immediately after opening the third different game in a row, "iaio" (grandpa, I guess). -- Backtrace (Reduced): #6 MemoryManager::new_from_block (this=0x55716d1727e0, s=72) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/memory.cpp:165 #7 0x000055716ab214a7 in Solver<22ul>::pack_position (this=this@entry=0x55716d5bbe20) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:209 #8 0x000055716ab2195e in Solver<22ul>::insert (this=this@entry=0x55716d5bbe20, cluster=cluster@entry=0x7ffcb4e6edbc, d=0, node=node@entry=0x7ffcb4e6edc0) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:873 #9 0x000055716ab21a4a in Solver<22ul>::new_position (this=this@entry=0x55716d5bbe20, parent=parent@entry=0x0, m=m@entry=0x7ffcb4e6ee00) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:906 #10 0x000055716ab290e6 in Solver<22ul>::doit (this=0x55716d5bbe20) at /chakra/desktop/kpat/src/kpat-18.12.2/patsolve/patsolve.cpp:487
*** This bug has been marked as a duplicate of bug 395624 ***