https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #3 from RJVB <rjvber...@gmail.com> --- Created attachment 105430 --> https://bugs.kde.org/attachment.cgi?id=105430&action=edit my current test patch Good to see this confirmed and bumped to a higher priority. I've attached the patch I'm currently running (since creating this ticket) in hope of finding at least an acceptable way to avoid hanging in production builds. I noticed that the check I once had against the most obvious dead-looping situation (currentIndex == previousIndex) had gone missing so I've re-introduced it. No idea if returning instead of aborting is an appropriate way to handle this kind of unexpected situations but it's probably no worse than NOT returning and continuing execution as if the assert wouldn't have failed :) -- You are receiving this mail because: You are watching all bug changes.
