Closed alex closed 7 years ago
This is a video demonstrating this problem (sorry it's in a .zip
, github doesn't allow uploading .mov
files).
Here's a description of what you see:
cmd-p
cmd-p
Thanks for taking the time to contribute!
We noticed that this is a duplicate of https://github.com/atom/fuzzy-finder/issues/88. You may want to subscribe there for updates.
Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.
This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!
Prerequisites
Description
When using atom with a gargantuan repo (in my case, all of Firefox: https://hg.mozilla.org/mozilla-central), the fine-file dialog (cmd-p) experiences significant performance problems. It is generally not able to keep up with the speed at which I type, leading to confusion.
When I say doesn't keep up with the speed at which I type, I don't mean it can't search that fast, I mean that rendering the keys I'm typing is delayed, often for many seconds.
Steps to Reproduce
Expected behavior: The letters I type are rendered instantly, even if the search can't be completed instantly
Actual behavior: The UI jerks around, the letters I type take multiple seconds to appear on the screen
Reproduces how often: Nearly always
Versions
macOS 10.12.4