Unable to launch profile, austin process exited with code -4058

[CamilleHamon]

Hello,
I installed Austin on windows (from the installer) and the VSC extension.
When I try to run the profiler in VSC extension, I get the following error:

Executing task: austin: profile c:\Users\camilleha\OneDrive - RISE\Dokument\MyPythonPackages\ElectricityMarketsData\src\ElectricityMarketsData\create_price_scenarios_AS.py

Starting Profiler in c:\Users\camilleha\OneDrive - RISE\Dokument\MyPythonPackages\ElectricityMarketsData.
Running '"C:\Program Files\P403n1x87\Austin"' with args '-i 100 --pipe C:\Users\camilleha\Anaconda3\envs\latestpkgs\python.exe "c:\Users\camilleha\OneDrive - RISE\Dokument\MyPythonPackages\ElectricityMarketsData\src\ElectricityMarketsData\create_price_scenarios_AS.py"'.
spawn "C:\Program Files\P403n1x87\Austin" ENOENTaustin process exited with code -4058

• The terminal process failed to launch (exit code: -4058).
• Terminal will be reused by tasks, press any key to close it.

I read in other issues that there may be some issues with whitespaces in the path. Is it what's happening here? (One of the parent folders of the python script is called "OneDrive - RISE").

[P403n1x87]

Hi @CamilleHamon. It's likely this is due to the whitespaces, even though it seems that all arguments with spaces are enclosed in quotes. Is PowerShell the default shell by any chance? Would you be able to switch to cmd instead. Otherwise, could you make a copy of the script to a place with no spaces just to check whether this is indeed the issue? Thanks 🙏

[CamilleHamon]

Thanks for the fast answer. I tried with cmd but get the same error. Unfortunately,the script uses quite a lot of files and I can't move them all.

[P403n1x87]

Thanks for the extra feedback. I'll try to have a look as soon as I have some time. In the meantime, perhaps you could try using Austin directly from the command line and open the data with the VS Code extension. It might not give you the same smooth experience, but hopefully it's still better than nothing 🙂

[CamilleHamon]

Thanks! I will try with the command line.

[eric6204]

I am having a similar issue but I do not have any spaces in my paths. I am using VSCode with the austin extension v0.13.1

*  Executing task: austin: profile c:\Dev\MyProjects\SEER\seer\seer.py

Starting Profiler in c:\Dev\MyProjects\SEER.
Running 'austin' with args '-i 100 --pipe c:\Dev\MyProjects\SEER\.venv\Scripts\python.exe c:\Dev\MyProjects\SEER\seer\seer.py'.
spawn austin ENOENTaustin process exited with code -4058

*  The terminal process failed to launch (exit code: -4058). 
*  Terminal will be reused by tasks, press any key to close it.

Unfortunately I cannot use the CLI version on my endpoint it has to be through VSCode.

[P403n1x87]

@CamilleHamon @eric6204 I have just noticed you both are reporting a ENOENT, which I believe indicates that the file (the Austin binary in this case) is not being found.

spawn "C:\Program Files\P403n1x87\Austin" ENOENTaustin process exited with code -4058

spawn austin ENOENTaustin process exited with code -4058

@CamilleHamon in your case I think this is because the path you have specified in the config only points to the folder where austin.exe is, instead of pointing to the executable itself. So hopefully using C:\Program Files\P403n1x87\Austin\austin.exe should fix your problem.

@eric6204 In your case it looks like the austin binary is not on the PATH. Can I confirm with you that you have also installed Austin? The Austin binary does not come with the VS Code extension and needs to be installed separately.

[eric6204]

Ok, I just have the VSCode plugin and not the full executable. Thanks!

[CamilleHamon]

Thank you. I will try to set the path directly to the executable.

[P403n1x87]

@CamilleHamon did that fix your issue?

[CamilleHamon]

I haven't had time to try yet. Hopefully next week!

[aleqx]

Just stumbled upon this thread. I'm gettign this too. Running VSCode 1.92.2.

spawn "C:\Program Files\P403n1x87\Austin\austin.exe" ENOENTaustin process exited with code -4058

I can confirm the executable exists (latest release):

C:\>"C:\Program Files\P403n1x87\Austin\austin.exe" --version
austin 3.6.0

Extension config is:

[aleqx]

I got it to work by uninstalling the Windows msi package, and installing it using pip install austin-dist which installed it in P:\python38\Scripts