Hi all, I'm working on a graphics authoring app. Naturally, there are lots of primitives stored in variable size mem blocks. The quantity can easily exceed a couple of hundred thousand blocks. Loading such content into fresh memory is not the problem, however, after editing/changing the content the heap will be cluttered with small blocks.
It is not really feasible to load a new instance and reorganize all blocks there, although that might be a last effort solution. Is there any recommendation on how to overcome this problem? I thought about reserving a large chunk of memory (approx 1.7 GB to leave room for other allocations) using malloc at startup time and then manage all small blocks myself. Looks a bit like brute force though. (I'm not caring about mobile phone usage) On 68k-Macs Handles were used (int**) where a pointer was stored in a master block, and the code would access the location in the master block only. That made it possible to move mem blocks around and compact the heap. Could that be a solution? Thanks for your ideas! Coming from long years of C development I am thrilled with emscripten and the options it offers for new kinds of web apps! -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/a90cdc4a-a342-4195-af7e-625ca38a041bn%40googlegroups.com.
