Extension gets very slow after a few hours of use
trouve-antoine opened this issue · comments
Type: Bug
Since about two weeks the Jupyter extension often shows as unresponsive in the list of Running Extension. After launch, it starts to get slower after a few hours, to a point where running a cell with only 1+1 may take minutes.
The same notebooks work perfectly fine when I run Jupyter standalone and use in my browser.
Extension version: 2024.4.0
VS Code version: Code 1.89.0 (Universal) (b58957e67ee1e712cebf466b995adf4c5307b2bd, 2024-05-01T02:10:10.196Z)
OS version: Darwin arm64 23.4.0
Modes:
System Info
| Item | Value |
|---|---|
| CPUs | Apple M2 (8 x 24) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled webgpu: enabled |
| Load (avg) | 3, 3, 4 |
| Memory (System) | 16.00GB (1.61GB free) |
| Process Argv | hafh-analytics --crash-reporter-id a522f206-f325-475e-92e4-aaa55a98363f |
| Screen Reader | no |
| VM | 0% |
A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
2e7ec940:31000449
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
ccp2r3:30993541
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
945dj816:31013170
pythoncenvpt:31022790
dwnewjupytercf:31035177
Please could you enable logging as follows:
- Open settings & go into
Jupyter->Logging - Change the value to
verbose - Reload VS Code,
- Attempt to repro the issue & then copy the output from the
Jupyteroutput panel.