I think it is likely an Electron’s bug since the app doesn’t hang while recording a performance profile in Developer Tools
But I can’t find any related issues on their repository on GitHub…strange.
Not sure if this is related or deserves its own thread, but I have been experiencing considerable input lag since upgrading to Sonoma. I have confirmed that this isn’t just a general system issue: vim in terminal, other apps do not have the same input lag.
I have vim motions plugin active. I’m not sure what causes it.
Well, it was so hard to identify the cause of the issue and I think I managed to solve it.
It happens when the app tries to access remote objects on a key event.
It is so strange because accessing remote objects must not be anything to do with CapsLock, so it is surely an Electron or chromium’s bug
I implemented a workaround for this issue in v5.6.3-beta.0.
@anon82854204 Yeah that sounds strange but I don’t have such an issue in my environment except for the CapsLock one. Please let me know if the issue persists in v5.6.3-beta.0!
Hello @craftzdog , unfortunately I’m still getting the issue
With the new version, however, it happens only the first time I turn the Caps Lock on.
After that, I can use the Caps Lock as expected.
I suspect that why it happens only the first time you turn the Caps Lock on right after the launch is that the app tries to access the data store via remote objects in the background for sync.
Does it still happen after the sync is finished?