- From: Robert O'Callahan <robert@ocallahan.org>
- Date: Thu, 16 Jul 2015 14:42:33 +1200
- To: Mike Kamermans <nihongo@gmail.com>
- Cc: "www-font@w3.org" <www-font@w3.org>
Received on Thursday, 16 July 2015 02:43:08 UTC
On Thu, Jul 16, 2015 at 4:46 AM, Mike Kamermans <nihongo@gmail.com> wrote: > Yeah,that's the conclusion we had to draw too - debugging the running > process revealed that the emscripten'd library was allocating three massive > array buffers (~313MB each), just by loading the library, so that's either > a nasty emscripten bug, or could be a deferred allocation pattern that > works in C++ but turns into instant allocation in JS. > It sounds like you must be instantiating the asm.js module three times, since normally there would be just one heap array per instance. Anyway, I think you should work this out with the emscripten community, since there's clearly a problem and it shouldn't be hard to diagnose and fix. Rob -- lbir ye,ea yer.tnietoehr rdn rdsme,anea lurpr edna e hnysnenh hhe uresyf toD selthor stor edna siewaoeodm or v sstvr esBa kbvted,t rdsme,aoreseoouoto o l euetiuruewFa kbn e hnystoivateweh uresyf tulsa rehr rdm or rnea lurpr .a war hsrer holsa rodvted,t nenh hneireseoouot.tniesiewaoeivatewt sstvr esn
Received on Thursday, 16 July 2015 02:43:08 UTC