Thanks, I'll do that.
On Tuesday, 21 April 2020 14:34:35 UTC+1, Ulan Degenbaev wrote:
>
> The backing store of an ArrayBuffer is allocated off the heap. Only a
> small JS object is allocated on the heap. That's why you see only 176 byte
> objects in the heap snapshot.
>
> That said, a loop
The backing store of an ArrayBuffer is allocated off the heap. Only a small
JS object is allocated on the heap. That's why you see only 176 byte
objects in the heap snapshot.
That said, a loop doing "dataCopy = new Uint8Array(message.data, 0);"
should trigger only minor GCs unless dataCopy is
I'm trying to understand some garbage collection behavior I'm seeing with
V8 / Chrome. The scenario is that I have a small program that receives ~
1MiB of image data from a websocket at a rate of about 60Hz.
Minimal receiving code looks like this:
var connection = new
