-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Constant Python segmentation fault when using VSCode #2693
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
pretty sure this means someone did
Why are we trying to dereference 8? |
I can reproduce this segmentation fault 100% of the time. All I have to do is quit and relaunch or reload VS Code. |
If you look at the top of your stack trace it looks like scikit-learn is crashing when we are asking Python to tell us details about the module:
What version of scikit-learn do you have installed and is it the latest version? |
According to |
I reinstalled scikit-learn to the new release (today's 0.20.0) and the segfault persists. Here is the crashlog under 0.20.0:
|
I'll see if I can verify on my personal Mac. |
If you need me to install/enable something to get some deeper logging I can–for me this is 100% reproducible with a launch/reload of VS Code. |
To be perfectly honest, @ReagentX , every other time we have seen this kind of crash it's because of a corrupt Python install or some C extension module behaving badly. I'll still give it a try to reproduce, though. |
I just tried importing scikit-learn 0.20.0 on my Mac using a brew-installed version of Python 3.7 and it works for me, so I don't think this is being caused by the extension itself, it's just causing Python to run and that happens to trigger a failure. As I have said I have seen this happen when an install of Python is corrupted, so I would try uninstalling Python entirely and doing a clean re-install. Otherwise the crash is in scikit-learn and so perhaps it is in there? But I would try re-installing Python first. But unfortunately I'm going to need to close this as it's not reproducible and everything points to it not being the extensions fault. |
Uh oh!
There was an error while loading. Please reload this page.
Environment data
Actual behavior
Python has a segmentation fault, but everything runs normally
Expected behavior
There is no segmentation fault
Steps to reproduce:
Logs
Output for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)Output from
Console
under theDeveloper Tools
panel (toggle Developer Tools on underHelp
)MacOS Crash Log
The text was updated successfully, but these errors were encountered: