https://bugs.kde.org/show_bug.cgi?id=368372
--- Comment #6 from Ugo Paternostro <ugo....@paternostro.org> --- Hi Christoph, do you mean that the stack trace labeled "KCrash" is different? One origins from QHash::remove and the other from QListData::realloc_grow? I will gladly try to run krunner via valgrind, I think the best I can do is replace krunner with a tiny script that runs valgrind, as it is started at login time and the crash usually happens if I use it in the first seconds after login, so I would like to avoid logging in, opening a shell, killing krunner and launching it via valgrind. Any comments on this? I'm sorry the crash is, at the moment, not so easily reproducible, so you'll have to wait and cross your fingers ;) TIA -- You are receiving this mail because: You are watching all bug changes.
