Skip to content
This repository was archived by the owner on Apr 14, 2022. It is now read-only.

Background python parser crashes importing sklearn.cluster in VS2017 #713

Closed
int19h opened this issue Mar 6, 2019 · 5 comments
Closed

Comments

@int19h
Copy link

int19h commented Mar 6, 2019

@jaybo commented on Mon Mar 04 2019

Environment data

  • PTVSD version: 4.2.0 and 4.2.4
  • OS and version: Windows 10, 1607, 14393.2670
  • Python version (& distribution if applicable, e.g. Anaconda): Anaconda 3.6.8
  • Using VS Code or Visual Studio: VS2017, 15.9.7

Actual behavior

Background code parser crashes importing sklearn.cluster.

Expected behavior

The background code parser should never crash. On PTVSD 4.2.0 If I dismiss the crash dialog, it will reappear after about one minute, presumably when the background parser is auto-restarted.

Steps to reproduce:

  1. pip install scikit-learn

  2. Load a python script which can be as simple as:

from sklearn.cluster import KMeans
  1. Wait a moment, then:
    image

  2. The program will run successfully.


@int19h commented on Wed Mar 06 2019

Could you clarify the steps to reproduce - is there another step there to launch it somehow, e.g. F5? Or by "load", do you mean just opening it in the editor and then waiting?


@jaybo commented on Wed Mar 06 2019

Just opening it in the editor and then waiting a moment will trigger the problem.

@jakebailey
Copy link
Member

Should this have gone to PTVS?

@int19h
Copy link
Author

int19h commented Mar 6, 2019

It looks like it's the language server itself that's crashing, so probably not VS-specific.

@MikhailArkhipov
Copy link

But the screenshot shows 'python'? LS process name is not python I believe. @huguesv - have you seen OOP analyzer crashes popping crash box?

@jakebailey
Copy link
Member

I think I've seen this happen in macOS (a different popup of course), which I believe is stemming from the OS detecting a crash in the scraper, which we are able to handle, but the OS trying to be helpful and showing that something broke/wasn't responding.

@jakebailey
Copy link
Member

jakebailey commented May 1, 2019

This was fixed in #740. It'd likely still break in PTVS until it gets updated.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants