brackets-archive / bracketsIssues

Archive of issues in brackets.
0 stars 0 forks source link

[CLOSED] Brackets unusably slow after Ctrl+Shift+F search #6255

Open core-ai-bot opened 3 years ago

core-ai-bot commented 3 years ago

Issue by tyunderwood Monday Feb 17, 2014 at 21:58 GMT Originally opened as https://github.com/adobe/brackets/issues/6901


I searched my whole project for a phrase with ctrl+shift+f and Brackets crashed. It's been unusably slow after that even when I completely reinstall brackets. Any help?

core-ai-bot commented 3 years ago

Comment by RaymondLim Monday Feb 17, 2014 at 22:06 GMT


@tyunderwood Are you having the issue with sprint 36? We do have one internal report of similar issue with sprint 36, but still cannot nail down to the real cause.

core-ai-bot commented 3 years ago

Comment by tyunderwood Monday Feb 17, 2014 at 22:07 GMT


yes, using the latest Brackets. Can I clear the problem out somehow?

On Mon, Feb 17, 2014 at 5:06 PM, Raymond Lim notifications@github.comwrote:

@tyunderwood https://github.com/tyunderwood Are you having the issue with sprint 36? We do have one internal report of similar issue with sprint 36, but still cannot nail down to the real cause.

Reply to this email directly or view it on GitHubhttps://github.com/adobe/brackets/issues/6901#issuecomment-35327262 .

core-ai-bot commented 3 years ago

Comment by RaymondLim Monday Feb 17, 2014 at 22:39 GMT


Unfortunately, no. You can try to use sprint 35 if you don't have the issue before. But it will be great if you can stick with sprint 36 and help us to nail down the root cause.

core-ai-bot commented 3 years ago

Comment by tyunderwood Monday Feb 17, 2014 at 22:41 GMT


I would love to help if there's anything I can do to troubleshoot. On Feb 17, 2014 5:40 PM, "Raymond Lim" notifications@github.com wrote:

Unfortunately, no. You can try to use sprint 35 if you don't have the issue before. But it will be great if you can stick with sprint 36 and help us to nail down the root cause.

Reply to this email directly or view it on GitHubhttps://github.com/adobe/brackets/issues/6901#issuecomment-35329750 .

core-ai-bot commented 3 years ago

Comment by RaymondLim Tuesday Feb 18, 2014 at 22:26 GMT


@tyunderwood You can try to install this extension https://github.com/gruehle/exclude-folders/ to exclude some folders from your project and see that fixes the issue. Note that the extension only excludes node_modules folder by default and you will need to modify the code to exclude more folders if you suspect anything other than node_modules in your project.

core-ai-bot commented 3 years ago

Comment by dangoor Monday Feb 24, 2014 at 19:27 GMT


Reviewed medium priority to@RaymondLim to continue gathering details

core-ai-bot commented 3 years ago

Comment by njx Thursday Feb 27, 2014 at 21:57 GMT


Adding performance tag.@tyunderwood - could you say how big your project is?

core-ai-bot commented 3 years ago

Comment by tyunderwood Thursday Feb 27, 2014 at 22:04 GMT


It's an enterprise Magento project, lots of files. On Feb 27, 2014 4:57 PM, "Narciso Jaramillo" notifications@github.com wrote:

Adding performance tag.@tyunderwood https://github.com/tyunderwood - could you say how big your project is?

Reply to this email directly or view it on GitHubhttps://github.com/adobe/brackets/issues/6901#issuecomment-36296610 .

core-ai-bot commented 3 years ago

Comment by peterflynn Wednesday Mar 05, 2014 at 19:33 GMT


@tyunderwood

A couple questions for clarity:

  1. When is Brackets slow? All the time, or only after you've run Find in Files? If you close the Find in Files results panel, does performance improve?
  2. Are all operations slow, or just certain actions? If typing feels slow, is this true in all files, or just certain file types? (e.g. try typing in a .txt file to see if that feels any different from .js)
  3. How many files are in your project overall? (In Windows you can find this out by right-clicking a folder and going to Properties, then wait for the totals to stop counting upwards).
core-ai-bot commented 3 years ago

Comment by peterflynn Thursday Mar 06, 2014 at 18:40 GMT


Possibly fixed by #7106, along with #6923 -- but hard to tell without getting more info from the filer. Leaving open for now. @tyunderwood do you have a sec to answer the questions above?

core-ai-bot commented 3 years ago

Comment by tyunderwood Friday Mar 07, 2014 at 16:05 GMT


Ok, taking a hard look at it to answer your questions the best I can.

1 Brackets is slow when navigating between files, and it frequently hangs up when entering text. There is no visible feedback with almost anything that I do, but several seconds (10+ seconds) it switches to whatever file or opens a menu.

Additionally, when I open brackets THIS time, it gives an error indexing files, saying the maximum number of files has been indexed. Not sure what this means, hasn't happened before.

2 All operations are slow, opening files and menus, pressing buttons, typing text, with several seconds of delay to do anything except for typing, which is intermittently slow.

3 one project I am working with is 4 gigs and 40,127 files. another is 1.1 gigs and 30,695 files.

This probably includes cache, media folders, and various non-editing files in the folder. they are local instances of Magento that I am currently running in a XAMPP server.

core-ai-bot commented 3 years ago

Comment by peterflynn Friday Mar 07, 2014 at 19:25 GMT


@tyunderwood Can you clarify though -- is Brackets slow as soon as you launch it? Or only after you do a Find in Files search? If the latter, does it speed up again when you close the search results?

core-ai-bot commented 3 years ago

Comment by tyunderwood Friday Mar 07, 2014 at 19:51 GMT


I have done a Find in Files exactly once, it has been slow to navigate the file tree and open files and start the software every time I have used it since. I uninstalled Brackets 36 and reinstalled it, and even installed Brackets 35 and it's still miserably slow. I assume it's something in the registry at this point.

core-ai-bot commented 3 years ago

Comment by peterflynn Tuesday Mar 11, 2014 at 00:05 GMT


Removing 'fix in progress' tag & moving out to Sprint 38 since this doesn't seem like the same issue as #6923.

@tyunderwood Can you try deleting your cache & preferences as described here - https://github.com/adobe/brackets/wiki/Cache-Folder. Does that change the behavior?

Has anything else changed on your system recently, such as a graphics driver update perhaps?

core-ai-bot commented 3 years ago

Comment by tyunderwood Friday Mar 14, 2014 at 17:52 GMT


it seems that deleting the cache folder has helped a lot, though I've not tested everything yet and I haven't restored my settings.

core-ai-bot commented 3 years ago

Comment by peterflynn Tuesday Mar 18, 2014 at 01:38 GMT


Closing since that seems to have done the trick. @tyunderwood please let us know if the problem comes back?

core-ai-bot commented 3 years ago

Comment by unwork Thursday Feb 25, 2016 at 18:24 GMT


I had the same issue, instant search was either very slow or not working altogether. Deleting the cache didn't help, but disabling instant search in preferences did fix it:

"findInFiles.instantSearch": false,
"findInFiles.nodeSearch": false,
core-ai-bot commented 3 years ago

Comment by abose Friday Feb 26, 2016 at 04:14 GMT


What is the machine config? how many files were there in the project? does this slowness happen all the time? can you post help>health reporthere?

core-ai-bot commented 3 years ago

Comment by unwork Friday Feb 26, 2016 at 20:08 GMT


What is the machine config?

iMac (27-inch, Late 2009) 2.8 GHz Intel Core i7 8 GB 1067 MHz DDR3 ATI Radeon HD 4850 512 MB 1TB Internal SSD

how many files were there in the project?

11600

does this slowness happen all the time?

Yes, the slowness is pretty consistent, regardless of what background processes might be going on. If I disable instantSearch and nodeSearch, as described above, the search results appear 75% faster.

can you post help>health reporter? Brackets - Health Report - 160226.txt

core-ai-bot commented 3 years ago

Comment by abose Saturday Feb 27, 2016 at 04:27 GMT


Do you have lots of programs[or lot of google chrome tabs] open? It looks like the memory availability could be low. Check in the system Monitor about the memory availability and usage. Else in this configuration, there shouldn't be any slowness.

can you Relaunch brackets,

  1. enable instantSearch and nodeSearch,
  2. switch between projects, then do some search ops within the project. do it for each of the projects that appear to be slow after the indexing is complete.
  3. post the health report after using brackets for a couple of minutes here.
  4. post debug>open console and paste the console logs here.
  5. How log does it take for the indexing to be complete?
core-ai-bot commented 3 years ago

Comment by unwork Monday Feb 29, 2016 at 18:45 GMT


Do you have lots of programs[or lot of google chrome tabs] open?

Not really. Whenever I use Brackets the only applications I might have open are Safari, Firefox and Chrome, each one with no more than 3-4 tabs with light website content on them, Transmit and iTunes. Activity Monitor does not report any processor activity over 2-6%

After following your steps above, I've noticed that switching between projects made a difference: I switched between two different versions of the same project, and performing the same global searches was quicker on one of them. The only difference between these projects, other than some minor file discrepancies, is their location: One of them (the faster one) is located on a non-OS partition separate from the startup up partition, the other one (the slower one) is located in my Sites folder inside my home directory, which obviously resides in the OS partition. Could this make a difference?

Health Report attached. Brackets Health Report 160229.txt

core-ai-bot commented 3 years ago

Comment by ErikVerheul Saturday Feb 16, 2019 at 16:17 GMT


Unwork's solution worked for me. My release is Release 1.13 build 1.13.1-17699 (windows-release-1.13.1 fc2ebbeea) I added these lines to the preferences file: "findInFiles.instantSearch": false, "findInFiles.nodeSearch": false,

Now I do not see "brackets indexing for instant search" endlessly anymore.