miloaissatu

> Do you see any errors in the terminal where you run Jupyter Notebook at the time of your crash? If so, can you include these in this issue? Nothing...

> I tried opening the notebook in JupyterLab Desktop (3.6.1-1) and did not see the crash mentioned. Might be specific to Notebook 6, not Lab. I had similar behaviour on...

[Dockerfile.txt](https://github.com/jupyter/notebook/files/11329153/Dockerfile.txt) Dockerfile building FROM dockerhub python:3.11.3 jupyterlab interface -> new notebook -> run `import warnings; warnings.filterwarnings('once'); !df -h` = crash jupyter lab -> classic notebook interface -> new notebook ->...

> Do you see any errors in the terminal where you run Jupyter Notebook at the time of your crash? If so, can you include these in this issue? Nothing...

did a more vanilla approach and had the same crash Dockerfile ``` FROM python:3.11.3-bullseye EXPOSE 8888 ```` then ``` docker build -t simple . docker run --rm -it --ip=0.0.0.0 -p...

I didn't use the official docker stacks images as I didn't see a python3.11 version available.

@RRosio ### & @JasonWeill , were you using conda/mamba/micromamba to install jupyter components and dependencies when attempting to reproduce the crash? i've been able to consistently reproduce this behaviour on...

couldn't reproduce it on ipython, something to do with jupyter-clientipykernel. looks like anything newer than jupyter-client==7.2.0+pyzmq==22.2.1 has this issue

update - can't reproduce the issue after installing the respective OS' zeromq-devel or equivalent, then pyzmq with pip install --no-binary had some indication from doing a diff on conda's pyzmq...

Hi @RRosio , @JasonWeill , no that issue doesn't seem related imo. I haven't been able to reproduce my problem since having pip install pyzmq via source instead of the...