very large memory footprint? about fontkit

[devongovett]

My guess is that it's brotli, which is the compression format used by WOFF2. It's an Emscripten compile, so there is probably a huge typed array in there...

[devongovett]

Not seeing that high memory usage either. Looks like about 28MB to me running your snippet unchanged, or 13MB with brotli disabled. How did you measure, what version of node are you running, what OS, etc?

[Pomax]

Windows 7, running node 0.12.7, measurement is based on windows's process monitor for the node.exe process

[Pomax]

Memory analysis using node-inspector shows a massive amount of memory used by JSArrayBufferData objects (based on shallow, not even deep, memory footprint).

There are only 10 of these objects that the inspector can see, with three rather huge ones. Looking at which contained functions these things have, it does look like they're all from the brotli library

[devongovett]

Can you comment out the require('brotli') call in node_modules/fontkit/src/WOFF2Font.js and try it?

[Pomax]

With brotli's requirement simply set to brotli = false; // require("brotli"); the memory footprint drops to a paltry 34MB, so it looks like brotli is doing really weird things on Windows...

[devongovett]

Grr. I wanted to do a real JS port rather than use an Emscripten compile anyway, because the Emscripten generated source is really huge, which sucks for browsers. Guess this is just another reason.

[Pomax]

how do you want to track? close this issue and open a new on on the brotli repo, or keep this one open as reminder?

[devongovett]

foliojs/brotli.js#3