Bug #1190
Own malloc() implementation conflicts with Bionic's one
Start date:
12/17/2015
Due date:
% Done:
100%
Estimated time:
CPU Architecture:
Host OS:
Toolchain:
Android version:
CrystaX Version:
Description
Currently, we have two malloc() implementations - one in Bionic, and one in libcrystax. This cause sporadic crashes, when memory allocated in one implementation somehow passed to the application part, where another implementation used, and then get deallocated.
This is artefact, which is left there by mistake, so we should completely remove own malloc() implementation until we completely get rid of Google's Bionic.
Updated by Dmitry Moskalchuk almost 5 years ago
- Status changed from In Progress to Closed
- % Done changed from 0 to 100