https://bugs.kde.org/show_bug.cgi?id=466229
--- Comment #7 from Stephan Kulow <co...@kde.org> --- I managed to trigger it. I had to make my computer busy (your's is recompiling the world, right? :) and play in one suit variant and click like a maniac. ==2602== Thread 9 SolverThread: ==2602== Invalid write of size 8 ==2602== at 0x484E41B: memmove (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==2602== by 0x46C539: UnknownInlinedFun (string_fortified.h:29) ==2602== by 0x46C539: Deck::update(Deck const*) (spidersolver2.cpp:656) ==2602== by 0x46D526: UnknownInlinedFun (spidersolver2.cpp:677) ==2602== by 0x46D526: UnknownInlinedFun (spidersolver2.cpp:802) ==2602== by 0x46D526: SpiderSolver2::patsolve(int) (spidersolver2.cpp:941) ==2602== by 0x423B86: SolverThread::run() (dealer.cpp:157) ==2602== by 0x5EE5E3C: QThreadPrivate::start(void*) (qthread_unix.cpp:330) ==2602== by 0x675698C: start_thread (in /usr/lib64/libc.so.6) ==2602== by 0x67DC343: clone (in /usr/lib64/libc.so.6) ==2602== Address 0x52dbf480 is 34,776,128 bytes inside a block of size 34,779,040 in arena "client" ==2602== -- You are receiving this mail because: You are watching all bug changes.
