| Summary: | Krita Next nightlies have significant lag during undo/redo/canvas input when editing large files | ||
|---|---|---|---|
| Product: | [Applications] krita | Reporter: | Tyson Tan <tysontanx> |
| Component: | * Unknown | Assignee: | Krita Bugs <krita-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | normal | CC: | ghevan, seitroth |
| Priority: | NOR | ||
| Version First Reported In: | nightly build (please specify the git hash!) | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Old kritarc from 5.2.6 or even earlier
New kritarc after resetting |
||
|
Description
Tyson Tan
2025-05-03 02:04:23 UTC
Does this happen in canvas-only mode? More specifically, does it happen with all three of the Layers, Overview, and Histogram dockers closed? I was trying to track down a similar issue where Ctrl+Z sometimes gets eaten/ignored (specifically, it fails to acquire a lock in KisDocument.cpp's undoImpl and gives up on undoing), and I think it might be the same or at least related to this. I suspect that the reduced idle delay in 5.3 for thumbnail generation is causing that lock to get held earlier making ignored undos easier to trigger (I noticed holding ctrl+z wouldn't cause it, but tapping with a specific slower cadence would). After raising the idle timeout in KisIdleTaskStrokeStrategy::preferredIdleWatcherInterval back up to 200ms from 50ms I haven't been able to reproduce my issue in my test case. I also tried the provided file at 200ms and 50ms, and while the things I'm noticing seem better at 200 it's still not perfect (it still ignores undo while thumbnails are generating), but seems to act the same as 5.2.9. No, it happens all the time regardless of the UI arrangement. I am unable to reproduce this bug. Changing the undo settings made no difference. Tested on macOS and Windows Nightly. I tested this bug on Windows and couldn't reproduce it either. Based on my experience with Krita nightlies, I suspected a configuration issue. After resetting my Krita configuration from the Settings menu, everything worked as expected. Since I typically use Krita with minimal configuration—just two shortcuts and panel positions— I believe the newer version has introduced some compatibility issues with old kritarc versions. I will attach the new and old versions of kritarc in later comments. Feel free to close this bug if you find it irrelevant. Created attachment 181808 [details]
Old kritarc from 5.2.6 or even earlier
Created attachment 181809 [details]
New kritarc after resetting
|