VSCode freezes if run as a background process on Linux (0.10.6) #1940

RussBaz · 2016-01-12T05:08:53Z

I could start it easily from a terminal as a background process in Fedora 23 (using ampersand). However, after an upgrade to 0.10.6 (64bit), it freezes soon after opening. It was not the case in the previous versions.

I suspect it might be related to the git integration somehow. It freezes if a folder is under git source control. It does not freeze otherwise. When I run it with the verbose option, it stops right before prompting for my repository credentials (which it normally does if not frozen).

vscode:
Version 0.10.6
Commit a80232b
Date 2015-12-19T11:26:42.359Z
Shell 0.34.5
Renderer 45.0.2454.85
Node 4.1.1

git:
2.5.0

Normal start-up (with a git repository address being changed):

bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
### VSCode main.js ###
/home/rbazhenov/Software/VSCode-linux-x64/resources/app { pathArguments: [ '/home/rbazhenov/Projects/ec+' ],
  programStart: 0,
  workers: -1,
  enablePerformance: false,
  verboseLogging: true,
  debugPluginHostPort: undefined,
  debugBrkPluginHost: undefined,
  logPluginHostCommunication: false,
  firstrun: false,
  openNewWindow: false,
  openInSameWindow: false,
  gotoLineMode: false,
  pluginHomePath: undefined,
  pluginDevelopmentPath: undefined,
  pluginTestsPath: undefined,
  disablePlugins: false }
Lifecycle#unload() 1
IPC#vscode-workbenchLoaded
Password for 'MYGITREPOADDRESS':

Failed start-up (freezes after opening):

bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
### VSCode main.js ###
/home/rbazhenov/Software/VSCode-linux-x64/resources/app { pathArguments: [ '/home/rbazhenov/Projects/ec+' ],
  programStart: 0,
  workers: -1,
  enablePerformance: false,
  verboseLogging: true,
  debugPluginHostPort: undefined,
  debugBrkPluginHost: undefined,
  logPluginHostCommunication: false,
  firstrun: false,
  openNewWindow: false,
  openInSameWindow: false,
  gotoLineMode: false,
  pluginHomePath: undefined,
  pluginDevelopmentPath: undefined,
  pluginTestsPath: undefined,
  disablePlugins: false }
Lifecycle#unload() 1
IPC#vscode-workbenchLoaded

The text was updated successfully, but these errors were encountered:

mdsitton · 2016-02-12T23:17:56Z

I'm fairly sure I'm having the same issue but instead of just freezing vscode it's also freezing my whole desktop environment(cinnamon)

mariusa · 2016-03-10T08:49:53Z

I also encounter freezing (using latest version now, but always got freezing since December when I start using it)
Using Fedora with default Gnome desktop.
$ uname -a
Linux localhost.localdomain 4.3.5-300.fc23.x86_64 #1 SMP Mon Feb 1 03:18:41 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Only vscode freezes, not anything else, after a few hours of usage.
Here's the terminal outout:

$ ./code --verbose
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
### VSCode main.js ###
/home/data/apps/VSCode-linux-x64/resources/app { pathArguments: [],
  programStart: 0,
  workers: -1,
  enablePerformance: false,
  verboseLogging: true,
  debugPluginHostPort: undefined,
  debugBrkPluginHost: undefined,
  logPluginHostCommunication: false,
  firstrun: false,
  openNewWindow: false,
  openInSameWindow: false,
  gotoLineMode: false,
  pluginHomePath: undefined,
  pluginDevelopmentPath: undefined,
  pluginTestsPath: undefined,
  disablePlugins: false,
  locale: undefined }
Lifecycle#unload() 1
IPC#vscode-workbenchLoaded
IPC#vscode-openFilePicker
IPC#vscode-openFilePicker
IPC#vscode-openFilePicker

<--- Last few GCs --->

96032349 ms: Mark-sweep 1394.7 (1457.6) -> 1394.7 (1457.6) MB, 2956.1 / 21 ms [allocation failure] [GC in old space requested].
96035276 ms: Mark-sweep 1394.7 (1457.6) -> 1394.7 (1457.6) MB, 2926.9 / 22 ms [allocation failure] [GC in old space requested].
96038180 ms: Mark-sweep 1394.7 (1457.6) -> 1394.7 (1457.6) MB, 2904.4 / 31 ms [last resort gc].
96041079 ms: Mark-sweep 1394.7 (1457.6) -> 1394.7 (1457.6) MB, 2898.1 / 29 ms [last resort gc].


<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0xa9cd183a859 <String[7]: file://>
    1: _completed [file:////home/data/apps/VSCode-linux-x64/resources/app/out/vs/workbench/workbench.main.js:~23] [pc=0x187c6d132853] (this=0x1c379e06a469 <JS Object>,e=0x3a3a717041b9 <undefined>)
    2: arguments adaptor frame: 0->1
    6: bound  [native v8natives.js:1208] [pc=0x187c61da8cb0] (this=0xa9cd1846061 <JS Global Object>)

==== Details ========================================...

Failed to get crash dump id.
Report Id: 
[VS Code]: detected unresponsive
Lifecycle#window-all-closed
Lifecycle#before-quit
App#dispose: deleting running instance handle

joaomoreno · 2016-03-10T09:16:41Z

@Tyriar is this solved with the new launcher?

Tyriar · 2016-03-10T20:22:27Z

I think so, no more need to use & as it's all handled by /usr/bin/code.

mariusa · 2016-03-10T21:45:40Z

For me it's freezing when launching in a terminal as
./code
and leaving the terminal open.
Will the fix mentioned address freezing in the next release?
Thanks

Tyriar · 2016-03-11T02:13:37Z

So the freezing happens when calling with ./code, not just ./code &? What console output are you getting? Does the window and/or UI appear?

What's coming in March may fix your problems, it's a new launch script and CLI. The launch logic past the command line args parsing hasn't changed much.

mariusa · 2016-03-11T06:49:41Z

So the freezing happens when calling with ./code -- yes.
It freezes after a few hours of usage, not instantly. VS Window remains frozen.
Console output is in the above comment, here's another

[marius@localhost VSCode-linux-x64]$ ./code --verbose
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
### VSCode main.js ###
/home/data/apps/VSCode-linux-x64/resources/app { pathArguments: [],
  programStart: 0,
  workers: -1,
  enablePerformance: false,
  verboseLogging: true,
  debugPluginHostPort: undefined,
  debugBrkPluginHost: undefined,
  logPluginHostCommunication: false,
  firstrun: false,
  openNewWindow: false,
  openInSameWindow: false,
  gotoLineMode: false,
  pluginHomePath: undefined,
  pluginDevelopmentPath: undefined,
  pluginTestsPath: undefined,
  disablePlugins: false,
  locale: undefined }
Lifecycle#unload() 1
IPC#vscode-workbenchLoaded
IPC#vscode-openFilePicker
IPC#vscode-openFilePicker

<--- Last few GCs --->

68220044 ms: Mark-sweep 1395.1 (1457.6) -> 1395.1 (1457.6) MB, 3072.1 / 17 ms [allocation failure] [GC in old space requested].
68223139 ms: Mark-sweep 1395.1 (1457.6) -> 1395.1 (1457.6) MB, 3095.2 / 17 ms [allocation failure] [GC in old space requested].
68226240 ms: Mark-sweep 1395.1 (1457.6) -> 1395.1 (1457.6) MB, 3100.4 / 25 ms [last resort gc].
68229369 ms: Mark-sweep 1395.1 (1457.6) -> 1395.1 (1457.6) MB, 3129.3 / 25 ms [last resort gc].


<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0x1460a833a859 <String[7]: file://>
    1: _completed [file:////home/data/apps/VSCode-linux-x64/resources/app/out/vs/workbench/workbench.main.js:~23] [pc=0x10d614784c73] (this=0x1dcb3a08cef1 <JS Object>,e=0x950159041b9 <undefined>)
    2: arguments adaptor frame: 0->1
    6: bound  [native v8natives.js:1208] [pc=0x10d606d9c670] (this=0x1460a8346061 <JS Global Object>)

==== Details =======================================...

Failed to get crash dump id.

Lifecycle#window-before-close 1
Lifecycle#unload() 1
Lifecycle#window-before-close 1
Lifecycle#unload() 1
[VS Code]: detected unresponsive
Lifecycle#window-all-closed
Lifecycle#before-quit
App#dispose: deleting running instance handle

Tyriar · 2016-04-04T15:53:50Z

@RussBaz @mariusa I can't reproduce this, can you try reproduce on the latest insider's build using the deb or rpm packages to install?

mariusa · 2016-04-06T11:41:15Z

@Tyriar installed the insiders rpm package 2 days ago, and now it froze.
There's no log to show, since I started it using the desktop shortcut.

Note that I haven't restarted vscode since starting it 2 days ago.

Tyriar · 2016-04-06T16:11:34Z

@bpasero @joaomoreno have you two seen the issue before that @mariusa has been experiencing?

bpasero · 2016-04-06T16:21:58Z

Is VS Code running out of memory after starting and causing it to crash?

mariusa · 2016-04-06T21:18:24Z

If there's any data I could provide next time (please see previous console output), I'd be glad to, just let me know exactly what/how please.

bpasero · 2016-04-07T05:24:17Z

To clarify: The freeze only happens when you open VS Code on a folder that prompts for git credentials?

mdsitton · 2016-04-07T05:50:26Z

That is correct in my case. (some others sound like they may be having other issues?)

I've had git support disabled to get around this though.

bpasero · 2016-04-07T06:03:53Z

I tried to reproduce on Ubuntu 15 and I am not even getting the git login dialog there, but VS Code otherwise works fine. @joaomoreno what is needed to get the dialog on Linux?

mariusa · 2016-04-07T07:22:46Z

The freeze only happens when you open VS Code on a folder that prompts for git credentials?
I have .git folders in the workspace, but it never asks me for credentials, and I use git only from command line. The freeze seems random to me, and unrelated to git.

joaomoreno · 2016-04-07T07:39:10Z

@bpasero #1796

bpasero · 2016-04-07T07:40:49Z

Maybe people have configured some special git credential helper that causes this?

joaomoreno · 2016-06-01T07:41:20Z

Closing as duplicate of #1796.

isidorn assigned joaomoreno Jan 12, 2016

joaomoreno added the bug Issue identified by VS Code Team member as probable bug label Jan 12, 2016

joaomoreno added this to the Backlog milestone Jan 12, 2016

Tyriar added the linux Issues with VS Code on Linux label Feb 3, 2016

mariusa mentioned this issue Mar 10, 2016

VSCode freezes up on Linux LXDE #1756

Closed

joaomoreno assigned Tyriar and unassigned joaomoreno Mar 10, 2016

Tyriar closed this as completed Mar 10, 2016

Tyriar reopened this Mar 11, 2016

Tyriar added the freeze-slow-crash-leak VS Code crashing, performance, freeze and memory leak issues label Apr 4, 2016

Tyriar closed this as completed Apr 4, 2016

Tyriar reopened this Apr 6, 2016

Tyriar added the git GIT issues label May 31, 2016

Tyriar assigned joaomoreno May 31, 2016

joaomoreno closed this as completed Jun 1, 2016

bpasero added the *duplicate Issue identified as a duplicate of another issue(s) label Jul 1, 2016

vscodebot bot locked and limited conversation to collaborators Nov 18, 2017

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

VSCode freezes if run as a background process on Linux (0.10.6) #1940

VSCode freezes if run as a background process on Linux (0.10.6) #1940

RussBaz commented Jan 12, 2016

mdsitton commented Feb 12, 2016

mariusa commented Mar 10, 2016

joaomoreno commented Mar 10, 2016

Tyriar commented Mar 10, 2016

mariusa commented Mar 10, 2016

Tyriar commented Mar 11, 2016

mariusa commented Mar 11, 2016

Tyriar commented Apr 4, 2016

mariusa commented Apr 6, 2016

Tyriar commented Apr 6, 2016

bpasero commented Apr 6, 2016

mariusa commented Apr 6, 2016

bpasero commented Apr 7, 2016

mdsitton commented Apr 7, 2016

bpasero commented Apr 7, 2016

mariusa commented Apr 7, 2016

joaomoreno commented Apr 7, 2016

bpasero commented Apr 7, 2016

joaomoreno commented Jun 1, 2016

VSCode freezes if run as a background process on Linux (0.10.6) #1940

VSCode freezes if run as a background process on Linux (0.10.6) #1940

Comments

RussBaz commented Jan 12, 2016

mdsitton commented Feb 12, 2016

mariusa commented Mar 10, 2016

joaomoreno commented Mar 10, 2016

Tyriar commented Mar 10, 2016

mariusa commented Mar 10, 2016

Tyriar commented Mar 11, 2016

mariusa commented Mar 11, 2016

Tyriar commented Apr 4, 2016

mariusa commented Apr 6, 2016

Tyriar commented Apr 6, 2016

bpasero commented Apr 6, 2016

mariusa commented Apr 6, 2016

bpasero commented Apr 7, 2016

mdsitton commented Apr 7, 2016

bpasero commented Apr 7, 2016

mariusa commented Apr 7, 2016

joaomoreno commented Apr 7, 2016

bpasero commented Apr 7, 2016

joaomoreno commented Jun 1, 2016