Thanks @madamov for sending me your project privately. It made a huge difference: I could reproduce the slowdown and test the fix against a project that actually exhibited it. I’ve kept it private and used it only for local testing.
I’ve now fixed the method parameter and description slowdown and the related class, window and property naming slowdown for the next release.
Several editing operations were triggering expensive project-wide work. I initially reduced the work happening on each keystroke, but testing with your project exposed another problem: preparing the inputs for background checking still happened on the UI thread after a short pause. That could block Studio for about two seconds, leaving characters queued until it finished.
The changes now:
- Update the edited source without repeatedly rebuilding the whole project or Navigator.
- Wait for a pause before scheduling checks.
- Prepare the project’s source and layouts on a background thread, allowing typing to continue.
- Discard obsolete checking results when newer edits arrive.
- Defer the expensive checking preparation when adding a method.
Across three repeated before/after runs using the same project, the worst measured typing delays were:
| Field | Before | After |
| Property name | 1,972 ms | 31 ms |
| Property type | 2,022 ms | 28 ms |
| Method parameters | 2,028 ms | 12 ms |
Adding a method also dropped from about 2.1 seconds to 14 ms.
Those are automated full-window measurements, including time spent waiting in the UI queue and rendering an offscreen frame. I’ve also tested the fix interactively in Studio and confirmed that typing is now responsive.
This will land in the next release.