Oxide library overrides malloc when it shouldn't

Bug #1595324 reported by Chris Coulson on 2016-06-22
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Chris Coulson

Bug Description

When compiled without the experimental allocator shim or tcmalloc, Chromium overrides glibc's malloc symbols (via base/process/memory_linux.cc) with wrappers that abort on failure. This is undesirable for Oxide because it means we change the allocator behaviour for embedders linked against us.

We only want this behaviour for child processes.

Changed in oxide:
importance: Undecided → Medium
status: New → Triaged
assignee: nobody → Chris Coulson (chrisccoulson)
Changed in oxide:
milestone: none → branch-1.17
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers