https://bugs.kde.org/show_bug.cgi?id=519276
--- Comment #7 from [email protected] --- Hi ja.krukowski and all, I am the author of the fix (MR !1204). I would like to clarify why this issue still persists in version 26.04.1. My fix was successfully merged to the `master` branch, but it has not been cherry-picked to the stable `release/26.04` branch yet. Therefore, the official 26.04.1 release still runs the unpatched code, which explains why the crash with `start=196, count=-90` is still showing up in your backtrace. With my patch applied, I have tested the exact reproduction steps and can confirm that the issue is fully resolved locally. Regarding bug 496530 and bug 488427 mentioned by TraceyC, those occurred when block selection was disabled and can no longer be reproduced. Hence, it is hard for me to identify any other potential crashing points under those scenarios. Could a maintainer please help cherry-pick the commit (from MR !1204) to the `release/26.04` branch so it can be included in the next point release (26.04.2)? Feel free to let me know if the bug still reproduces after the commit is cherry-picked. I am eager to see this bug completely resolved. Thank you! raycppwizard -- You are receiving this mail because: You are watching all bug changes.
