Project

General

Profile

Actions

Bug #1190

closed

Own malloc() implementation conflicts with Bionic's one

Added by Dmitry M. about 9 years ago. Updated about 9 years ago.

Status:
Completed
Priority:
Urgent
Assignee:
Category:
libcrystax
Target version:
Start date:
12/17/2015
Due date:
% Done:

100%

Estimated time:
CPU Architecture:
Host OS:
Toolchain:
Android version:
CrystaX NDK 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.

Actions #1

Updated by Dmitry M. about 9 years ago

  • CrystaX NDK Version changed from 10.0.0 to 10.3.0
Actions #2

Updated by Dmitry M. about 9 years ago

  • Status changed from Open to In Progress
Actions #3

Updated by Dmitry M. about 9 years ago

  • Status changed from In Progress to Completed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF