Project

General

Profile

Bug #1190

Own malloc() implementation conflicts with Bionic's one

Added by Dmitry Moskalchuk over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Urgent
Category:
libcrystax
Target version:
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.

History

#1 Updated by Dmitry Moskalchuk over 3 years ago

  • CrystaX Version changed from 10.0.0 to 10.3.0

#2 Updated by Dmitry Moskalchuk over 3 years ago

  • Status changed from Open to In Progress

#3 Updated by Dmitry Moskalchuk over 3 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF