We have an embedded real time system (Win-API compatible) with very limited memory (256) and with an different heap management. We discovered a problem with memory fragmentation. The system loses up to 4MB available memory for each newly created archive. We tried different buffer sizes without any success (SetAdvanced()). How can we avoid memory fragmentation while using the ZipArchive library?
ZipArchive uses all the available memory during closing segmented archives without throwing a bad_alloc exception. The size of the archives is up to 2GB. Why does ZipArchive reserves all memory for closing archives? How can we avoid this? Is there a set-method for limiting the memory usage? We also tried to set different commit modes without any success, the behavior is the same.
