6262c7a0bf
* Use fork instead of spawn We no longer do in-place updating so no need for the spawn. The advantage of a fork is that it preserves flags like --prof which you can use to profile code-server. Also I am not sure the comment about not being able to reload in place with fork was even true to begin with. * Refresh heartbeat patch Seems to have gotten out of date a little. * Propagate execArgv to extension host This will let us profile the extension host.
18 lines
843 B
Diff
18 lines
843 B
Diff
Preserve process.execArgv
|
|
|
|
This ensures flags like --prof are passed down so we can profile everything.
|
|
|
|
Index: code-server/lib/vscode/src/vs/server/node/extensionHostConnection.ts
|
|
===================================================================
|
|
--- code-server.orig/lib/vscode/src/vs/server/node/extensionHostConnection.ts
|
|
+++ code-server/lib/vscode/src/vs/server/node/extensionHostConnection.ts
|
|
@@ -228,7 +228,7 @@ export class ExtensionHostConnection {
|
|
|
|
public async start(startParams: IRemoteExtensionHostStartParams): Promise<void> {
|
|
try {
|
|
- let execArgv: string[] = [];
|
|
+ let execArgv: string[] = process.execArgv ? process.execArgv.filter(a => !/^--inspect(-brk)?=/.test(a)) : [];
|
|
if (startParams.port && !(<any>process).pkg) {
|
|
execArgv = [`--inspect${startParams.break ? '-brk' : ''}=${startParams.port}`];
|
|
}
|