https://bugs.kde.org/show_bug.cgi?id=473801
--- Comment #10 from Maik Qualmann <metzping...@gmail.com> --- There isn't really a crash, I see that it's at a Qt_ASSERT stop. They run Qt in debug mode or an environment variable is set so that every Qt_ASSERT leads to an abort. According to the Qt Doc, m_childCache.value(row, nullptr); would be valid. I suspect, but that if row is out of range Qt will do a Qt_ASSERT. I will take a look. Maik -- You are receiving this mail because: You are watching all bug changes.
