Notebook After uninstallation, the api is still called in the background

[chenjpu]

Using nextjs technology to integrate Notebook, when the navigation leaves the Notebook edit page, the api background continuously access。
When navigate to the Notebook edit page again, the shortcut keys all fail。

Description

Reproduce

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

Expected behavior

Context

• Datalayer version:
• Operating System and version:
• Browser and version:

Browser Output

[echarles]

Hi @chenjpu Are you using the simple Notebook component or the more evolved JupyterLabApp component?

How do you navigate away? (maybe the Notebook component is still rendered but not shown?)

[chenjpu]

using the simple Notebook component

use nextjs router（Only one page contains the Notebook component）

[chenjpu]

Force to refresh the browser, and the background api access stops. Is it the resource leakage caused by the service when the components are uninstalled?

[chenjpu]

@echarles

jupyter-ui/packages/react/src/components/lumino/Lumino.tsx

Lines 30 to 37 in 53f2cd6

	if (children.isAttached || children.node.isConnected) {
	children.dispose();
	Widget.detach(children);
	}
	} catch (e) {
	// no-op.
	// console.debug('Exception while detaching Lumino widget.', e);
	}

When the component is unloaded, the children.node.isConnected=false, lead to an exception. Does it have anything to do with this?

[echarles]

When the component is unloaded, the children.node.isConnected=false, lead to an exception. Does it have anything to do with this?

That could be the case. that exception is coming from Lumino and hard to remove (ideally it should be).

Maybe a temp workaround, a termination action on the Notebook hook could help.

[chenjpu]

Fix keydown Event leak(#265)

[chenjpu]

@echarles

useEffect(() => {
    return () => {
      try {
        kernelManager?.dispose();
        serviceManager?.dispose();
      } catch (e) {
        //console.log(e)
      }
    };
  }, [serviceManager, kernelManager]);

Clear some api calls, but there are still some other apis rotation :(