Windows applications become very unhappy when memory is allocated in one module (exe or dll) and deallocated in another. This is because each of the C run time library instances uses its own heap. Mixing allocating in one heap and deallocating in another will lead to memory leaks and heap corruption. For modules that build against roken avoid this problem by sharing roken's allocator with the module that uses it. Change-Id: I31e35c600a78350b168a281811160696dc327544
1.8 KiB
1.8 KiB