Own malloc() implementation conflicts with Bionic's one
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.
#3 Updated by Dmitry Moskalchuk over 3 years ago
- Status changed from In Progress to Closed
- % Done changed from 0 to 100