Hmm... dSnd is basically a queue - when you write to the socket, stuff gets added to it, and then when it's possible to send the data over the socket, the data from it gets sent and it's cleared.
Is this a proper 'leak' - as in - you type quit() and then leaked variables are reported? Or it's just that dSnd keeps growing? If it's growing I'd assume it is because for whatever reason the socket hasn't been able to send the data? Maybe it's closed? That could be a bit of a bug I guess - if it's closed it should error if you try and write to it.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Hmm...
dSnd
is basically a queue - when you write to the socket, stuff gets added to it, and then when it's possible to send the data over the socket, the data from it gets sent and it's cleared.Is this a proper 'leak' - as in - you type
quit()
and then leaked variables are reported? Or it's just thatdSnd
keeps growing? If it's growing I'd assume it is because for whatever reason the socket hasn't been able to send the data? Maybe it's closed? That could be a bit of a bug I guess - if it's closed it should error if you try and write to it.