vscode-jupyter: `aggdraw.Draw` causes kernel to die, not in web interface, only in VS Code

@DonJayamanne this is still happening ( extension version: v2023.10.1100000000 ):

# clearing all logs and restarting the kernel
22:53:03.023 [debug] Restart kernel command handler for ~/python/jupyter/notebooks/Mapping/Aggdraw-Test.ipynb
22:53:03.023 [debug] restart the kernel, options.disableUI=false for ~/python/jupyter/notebooks/Mapping/Aggdraw-Test.ipynb
22:53:03.023 [info] Restart requested ~/python/jupyter/notebooks/Mapping/Aggdraw-Test.ipynb
22:53:03.024 [debug] Cancel pending cells
22:53:03.160 [debug] Updating preferred kernel for remote notebook 6e451405-1639-472a-9b44-d7cd8d3a08ca
22:53:03.160 [info] Restarted 6e451405-1639-472a-9b44-d7cd8d3a08ca
22:53:03.160 [debug] Storing Preferred remote kernel for ~/python/jupyter/notebooks/Mapping/Aggdraw-Test.ipynb is 6e451405-1639-472a-9b44-d7cd8d3a08ca
22:53:03.160 [debug] Started running kernel initialization for ~/python/jupyter/notebooks/Mapping/Aggdraw-Test.ipynb
22:53:03.160 [debug] Executing silently Code (unknown) = try:\nimport ipywidgets as _VSCODE_ipywidgets\nprint("e976ee50-99ed-4aba-9b6b-9dcd5634d07d:IPy
22:53:03.500 [debug] Executing silently Code (completed) = try:\nimport ipywidgets as _VSCODE_ipywidgets\nprint("e976ee50-99ed-4aba-9b6b-9dcd5634d07d:IPy with 0 output(s)
22:53:03.500 [debug] Determined IPyWidgets Version as undefined and event fired
22:53:03.501 [debug] Executing silently Code (idle) = __vsc_ipynb_file__ = "~/python/jupyter/notebooks/Mapping/Aggdraw-Test.ipynb"\n%config Complete
22:53:03.506 [debug] Executing silently Code (completed) = __vsc_ipynb_file__ = "~/python/jupyter/notebooks/Mapping/Aggdraw-Test.ipynb"\n%config Complete with 0 output(s)
22:53:03.506 [debug] Requesting Kernel info
22:53:03.507 [debug] Got Kernel info
22:53:03.507 [debug] End running kernel initialization, now waiting for idle
22:53:03.507 [debug] Waiting for 60000ms idle on (kernel): 6e451405-1639-472a-9b44-d7cd8d3a08ca -> idle
22:53:03.507 [debug] Finished waiting for idle on (kernel): 6e451405-1639-472a-9b44-d7cd8d3a08ca -> idle
22:53:03.507 [debug] End running kernel initialization, session is idle
22:53:03.507 [debug] Registering commtarget jupyter.widget
# performing a run-all
22:53:11.557 [info] Handle Execution of Cells 0 for ~/python/jupyter/notebooks/Mapping/Aggdraw-Test.ipynb
22:53:11.558 [debug] start the kernel, options.disableUI=false for ~/python/jupyter/notebooks/Mapping/Aggdraw-Test.ipynb
22:53:11.558 [debug] Execution Request Sent to Kernel for cell 0
22:53:11.568 [debug] Start cell 0 execution @ 1701985991568 (clear output)
22:53:11.568 [info] Kernel acknowledged execution of cell 0 @ 1701985991568
22:53:11.589 [info] End cell 0 execution @ 1701985991589, started @ 1701985991568, elapsed time = 0.021s
22:53:11.590 [debug] Cell 0 executed with state Success
22:53:11.671 [debug] Executing silently Code (idle) = def _VSCODE_getVariable(what_to_get, is_debugging, *args):\n# Query Jupyter server for the info a
22:53:12.146 [debug] Start cell 0 execution @ 1701985991589
22:53:12.147 [error] Jupyter Extension (Error in requestVariables, method:requestVariables): Error: Canceled future for execute_request message before replies were done
    at t.KernelShellFutureHandler.dispose (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.10.1100000000-linux-x64/out/extension.node.js:2:32375)
    at ~/.vscode-server/extensions/ms-toolsai.jupyter-2023.10.1100000000-linux-x64/out/extension.node.js:2:26594
    at Map.forEach (<anonymous>)
    at y._clearKernelState (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.10.1100000000-linux-x64/out/extension.node.js:2:26579)
    at ~/.vscode-server/extensions/ms-toolsai.jupyter-2023.10.1100000000-linux-x64/out/extension.node.js:2:29022
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
22:53:12.222 [info] End cell 0 execution @ undefined, started @ 1701985991589, elapsed time = -1701985991.589s
22:53:12.257 [debug] Executing silently Code (unknown) = def _VSCODE_getVariable(what_to_get, is_debugging, *args):\n# Query Jupyter server for the info a

This cell is the only one in the notebook:

import aggdraw
from PIL import Image, ImageDraw
 
print('aggdraw version', aggdraw.__version__)
# aggdraw version 1.3.12 -- on aiohttp
# aggdraw version 1.3.16 -- in conda

# WARN `USE_AGGDRAW = True` causes the kernel to crash 
USE_AGGDRAW = True

img = Image.new("RGB", (256, 256), "white")

if USE_AGGDRAW:
    agg_draw = aggdraw.Draw(img)
else:
    draw = ImageDraw.Draw(img)

# Diagonal line
p1 = (0,0)
p2 = (255,255)

if USE_AGGDRAW:
    pen = aggdraw.Pen(color=(255,0,0), width=10, opacity=127)
    agg_draw.line((p1[0], p1[1], p2[0], p2[1]), pen)
else:
    draw.line([p1, p2], fill="red", width=10)

if USE_AGGDRAW:
    agg_draw.flush()

display(img)

and outputs this result:

aggdraw version 1.3.16

[image correctly rendered]

The Kernel crashed while executing code in the the current cell or a previous cell. Please review the code in the cell(s) to identify a possible cause of the failure. Click [here](https://aka.ms/vscodeJupyterKernelCrash) for more info. View Jupyter [log](command:jupyter.viewOutput) for further details.

It still applies that if the “Variables”-panel is collapsed, then the Kernel doesn’t crash.

Turns out that running only the following cell no longer triggers a Kernel crash, so apparently now the behavior is different:

import aggdraw
# print('aggdraw version', aggdraw.__version__) # = 1.3.16
d = aggdraw.Draw("RGB", (100, 100), (0,0,0))

This small cell used to cause the problem as well.

I noticed that in the example cell which does cause a crash, the “Variables”-panel does not show any variables at all (“no variables defined”)

Regarding the last added information with the two cells: This works in a simple notebook, but not in a larger one. In any case, closing the variable view “fixes” the issue 100%.