esp32 - tcp_server_blink example about atomvm HOT 2 CLOSED

I enabled TRACE to see more: a new connection appears in the netconn callback for which no event descriptor is registered:

connected {{192,168,2,104},{255,255,255,0},{192,168,2,1}} socket: init socket: creating server tcp netconn socket: opened event descriptor 0 in init_server_tcp_socket for netconn 0x3ffc30a4 socket: binding to IP_ADDR_ANY on port 44404 socket: bound to port 44404 socket: listening on port 44404 Listening on port 44404. Waiting to accept connection... socket: accepting tcp netconn socket: Found event descriptor in socket_driver_do_accept for netconn 0x3ffc30a4 socket: accepting tcp netconn COMPLETE socket: netconn callback, netconn: 0x3ffc30a4, evt: 0, len: 0 event_descriptor[0]: 0x3ffc30a4 socket: accepting callback socket: Found event descriptor in accept_callback for netconn 0x3ffc30a4 socket: netconn callback, netconn: 0x3ffc2d90, evt: 0, len: 344 event_descriptor[0]: 0x3ffc30a4 warning: event descriptor not found socket: event descriptor not found in socket_callback for netconn 0x3ffc2d90 abort() was called at PC 0x4014af3c on core 0 0x4014af3c: socket_callback at /home/florian/AtomVM/src/platforms/esp32/main/socket_driver.c:90

from atomvm.

The mentioned behaviour occurs with browser.
When I use nc 44404 it works nicely.
However when cancelling the nc command and issueing a new one a reboot occurs.

from atomvm.