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

Runaway memory usage when working with msticpy #923

Closed
jakebailey opened this issue Apr 10, 2019 · 1 comment
Closed

Runaway memory usage when working with msticpy #923

jakebailey opened this issue Apr 10, 2019 · 1 comment
Assignees
Milestone

Comments

@jakebailey
Copy link
Member

To reproduce:

  1. Clone https://github.com/Microsoft/msticpy
  2. Install dependencies in a venv (pip install -r requirements.txt)
  3. Open msticpy\nbtools\__init__.py.

Memory is stable until a point (I think when analyzing plotly) when the memory usage just grows and grows.

@AlexanderSher AlexanderSher self-assigned this Apr 10, 2019
jakebailey added a commit that referenced this issue Apr 10, 2019
Found in #923.

Is there an easy way to test this, or is this alright as-is?
@MikhailArkhipov MikhailArkhipov added this to the April 2019.1 milestone Apr 11, 2019
@MikhailArkhipov
Copy link

Plotly is the root case.

AlexanderSher added a commit to AlexanderSher/python-language-server that referenced this issue Apr 16, 2019
jakebailey added a commit to jakebailey/python-language-server that referenced this issue Nov 1, 2019
Found in microsoft#923.

Is there an easy way to test this, or is this alright as-is?
jakebailey pushed a commit to jakebailey/python-language-server that referenced this issue Nov 1, 2019
…crosoft#972)

* Fix microsoft#923: Runaway memory usage when working with msticpy

* - Fix sorting
- Mark session canceled if ast isn't set yet
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants