Server still running after calling client.stop()?

I’ve got the following code in my extension

	// create language client and launch server
	const pythonMain = context.asAbsolutePath(
		path.join('src', 'server', 'main.py')
	);
	const args = [pythonMain];
	// Add debug options here if needed
	const serverOptions: ServerOptions = { command: pythonInterpreter, args };
	const clientOptions: LanguageClientOptions = {
		documentSelector: [
			{ scheme: "file", language: "antimony" },
		],
	};
	// Create the language client and start the client.
	client = new LanguageClient(
		'AntimonyLanguage',
		'Antimony Language Server',
		serverOptions,
		clientOptions
	);
	// Start the client. This will also launch the server
	const clientDisposable = client.start();
	context.subscriptions.push(clientDisposable);

and

export function deactivate(): Thenable<void> | undefined {
	if (!client) {
		return undefined;
	}
	// shut down the language client
	return client.stop();
}

I’ve noticed that when I run my extension in debugging mode, even after I quit the extension I can still see the python process in my task manager, and if I run my extension 10 times, there will be 10 processes. Am I doing anything wrong?

[dbaeumer]

@vain0x this got already addressed in the latest next versions of the library:

Server: 8.0.0-next.5 and client: 8.0.0-next.7

[dbaeumer]

@mastevb will close the issue. Please ping if you have additional information.