-
Notifications
You must be signed in to change notification settings - Fork 28.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File search can exceed max string length #11842
Comments
@chrmarti fyi |
Same problem here. Find processes take nearly 100 percent of my CPU. |
The error appears to indicate the process ran out of memory. It looks like the find command doesn't always terminate or is spawned multiple times. Not sure if decoding might play a role here. @baoziv587 could you run @bpasero are there known issues with node's built-in string_decoder module, should I be using iconv-lite instead? |
the output672575727 |
@chrmarti iconv is only used to decode non-utf8 to utf8 and when utf8 is set it falls back to use the node.js decoder. You think this is an encoding issue? |
Not encoding related then. That string is simply too long. @baoziv587 Could you also run |
the output3285397 |
@chrmarti Perhaps because of these floders. If skip these folders ,there are alright @shaoshuai0102 you also install node_modules with cnpm? |
Thanks @baoziv587. I will use this report to track the string size problem and #11874 the underlying problem that we retrieve the entire file list before applying the exclusion filters. |
The underlying problem is fixed in the latest insiders build. Will still address this one. |
ok,thanks @chrmarti |
Verified by code review |
- VSCode Version: 1.5.1
- OS Version:mac OS X 10.11.6
Steps to Reproduce:
I can not get any file search result in my project after updating The latest version of vscode(1.5.1).
And i noticed that when i am typing some keyword of file name ,CODE will generate some subprocess do these search job with
80 percent of the CPU cost
Function decodeData(invoked by Class FileWalker) always got same error
('vs/workbench/services/search/node/fileSearch.ts').
I did not find out the reason , hope these info is helpful.
The text was updated successfully, but these errors were encountered: