jupyter-resource-usage icon indicating copy to clipboard operation
jupyter-resource-usage copied to clipboard

Not working (no update of memory usage) after updating to JupyterLab 3.6.2

Open adalseno opened this issue 2 years ago • 2 comments

Description

The info about RAM usage is not updated since I installed JupyterLab 3.6.2 Screenshot 2023-03-24 01 18 49 but the memory usage is much higher Screenshot 2023-03-24 01 22 31 With JupyerLab 3.6.1 it was working fine I have the same issue when running a notebook with R kernel (I don't remember if with 3.6.1 it was working; I usually use python kernels).

Reproduce

  1. Go to '...'
  2. Click on '...'
  3. Scroll down to '...'
  4. See error '...'

Expected behavior

RAM usage should update

Context

jupyter-resource-usage 0.7.2 installed via pip

  • Operating System and version:
  • Browser and version: Chrome Version 110.0.5481.181
  • Jupyter Server version: JupyterLab 3.6.2
Troubleshoot Output
Paste the output from running `jupyter troubleshoot` from the command line here.
You may want to sanitize the paths in the output.
Command Line Output
Paste the output from your command line running `jupyter lab` here, use `--debug` if possible.
Browser Output
Paste the output from your browser Javascript console here, if applicable.

adalseno avatar Mar 24 '23 00:03 adalseno

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! :hugs:
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively. welcome You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! :wave:
Welcome to the Jupyter community! :tada:

welcome[bot] avatar Mar 24 '23 00:03 welcome[bot]

Thanks @adalseno for the report.

The 3.6.2 release notes don't seem to include changes that could be related: https://github.com/jupyterlab/jupyterlab/releases/tag/v3.6.2

Would you be able to open the browser dev tools console and see if there are any error there? Or maybe the server logs also have more information? Thanks!

jtpio avatar Apr 04 '23 07:04 jtpio