1134923 - Remove NS_Alloc/NS_Realloc/NS_Free

Status: RESOLVED FIXED

(Core :: XPCOM, defect)

Description

[Mike Hommey [:glandium]]

Possibly relevant discussion in bug 958212. At this point, I don't think we need to keep the distinction for a "XPCOM" allocator. We're already doing all sorts of combination of allocators, and our increased use of "standard" C++ doesn't make the distinction any easier. A case could be made that a "XPCOM" allocator is still interesting for embedding and components, but I'd argue those already need mozalloc.

Comment 1

[Mike Hommey [:glandium]]

Attachment: Remove NS_Alloc/NS_Realloc/NS_Free

Comment 2

[Mike Hommey [:glandium]]

Comment on attachment 8566907 [details] [diff] [review]
Remove NS_Alloc/NS_Realloc/NS_Free

Gah, this one fails because mozalloc is not available to the standalone glue... I have to re-reorder my queue.

Comment 3

[Mike Hommey [:glandium]]

Attachment: Remove NS_Alloc/NS_Realloc/NS_Free

They are kept around for the sake of the standalone glue, which is used
for e.g. webapprt, which doesn't have direct access to jemalloc, and thus
still needs a wrapper to go through the xpcom function list and get to
jemalloc from there.

Comment 4

[Pulsebot]

https://hg.mozilla.org/integration/mozilla-inbound/rev/7bc6ca149561

Comment 5

[Ryan VanderMeulen [:RyanVM]]

https://hg.mozilla.org/mozilla-central/rev/7bc6ca149561