Version 0.10.3 uses a full core on CPU

[q42jaap]

Version 0.10.3 uses up 100% cpu on my macbook pro.
Especially the Electron Helper

[alexdima]

@q42jaap Can you please provide additional details.

Does this happen when opening a specific folder? Does this happen when opening VSCode without a folder (Cmd+Shift+N)? Anything you can add to help us reproduce

[q42jaap]

Im using the following line in .bash_profile:
code () { VSCODE_CWD="$PWD" open -n -b "com.microsoft.VSCode" --args $* ;}

I use that to code . in the directory. I leave the editor open voor a long time. And then I notice my Mac is running low on power. It's also getting hot, CPU is high on the Electron Helper subprocess.

It's difficult to say how to repro, I can't always get that to happen (fortunately).

tree | wc -l gives 25876 (406 of my own files/dirs, the rest are node_modules, I'm using npm 3)

[bpasero]

@q42jaap what workspace do you open with code?

[q42jaap]

I'm opening a directory in which I've checked out our private git repo. Not a particularly big project.
We use nodejs 5 for backend and babel ES6 code for the frontend.

Are there steps (suchs as logs or dumps) I can take and submit (privately) to Microsoft?

[bpasero]

@q42jaap well it would be interesting if this happen on a different folder too, maybe you could give it a try. Does the CPU go to 100% right after you open the folder?

[q42jaap]

It does not always happen, and it does not happen immediately. I'm currently in the process of reinstalling vscode, which is going to take a while due to slow connection.

[ragebiswas]

I'm seeing the same on 0.10.5. Strangely, I didn't see this prior to 0.10.5 - any ideas?

[bpasero]

Again, if there is a repository we could clone to reproduce the behaviour, please let us know.

[planetexpress69]

Same her. As of 0.10.5 ElectronHelper misbehaves and eats up all of my cpu cycles.
Happens on a small Ember project with a fairly big nodes_module directory. node_module and bower_components are already excluded from search. Is there a way to turn back to 0.10.3 without building it by yourself?
I am running on OS X 10.11.2.

Update: "files.ignore" does not help. Looks like ElectronHelper is trying to allocate all the memory it can get! Once its done eating up all memory it crashes. Incompatibility to Node 5.2.0?

brew upgrade node (to 5.3.0) does not help either...

Process: Electron Helper [1700] Path: /Applications/Visual Studio Code.app/Contents/Frameworks/Electron Helper.app/Contents/MacOS/Electron Helper Identifier: Electron Helper Version: 0 Code Type: X86-64 (Native) Parent Process: Electron Helper [1696] Responsible: Electron Helper [1700] User ID: 501

Date/Time: 2015-12-21 15:18:30.508 +0100
OS Version: Mac OS X 10.11.2 (15C50)
Report Version: 11
Anonymous UUID: 41A4E3F5-2072-E603-8E66-FF147EECEDD3

Time Awake Since Boot: 7100 seconds

System Integrity Protection: disabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Application Specific Information:
abort() called

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff8f973002 pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff90caf5c5 pthread_kill + 90
2 libsystem_c.dylib 0x00007fff869d16e7 abort + 129
3 libnode.dylib 0x00000001049b2189 0x1049a4000 + 57737
4 libnode.dylib 0x0000000104cf2d12 v8::internal::V8::FatalProcessOutOfMemory(char const, bool) + 594
5 libnode.dylib 0x0000000104e8c788 v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationSpace) + 408
6 libnode.dylib 0x00000001050de89d v8::internal::Runtime_AllocateInTargetSpace(int, v8::internal::Object_, v8::internal::Isolate_) + 109
7 ??? 0x000016c575e06355 0 + 25037342008149

[bpasero]

For those that see high CPU use, please identify the arguments for the proces (e.g. ps aux | grep ) so that we know which of the processes that Code spawns is the one in charge.