Closed
Bug 828845
Opened 12 years ago
Closed 4 years ago
about:memory reporter for the custom linker
Categories
(Core :: mozglue, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: glandium, Assigned: glandium)
References
Details
(Whiteboard: [MemShrink:P2])
No description provided.
|
||
Updated•12 years ago
|
Whiteboard: [MemShrink]
|
|
||
Updated•12 years ago
|
Whiteboard: [MemShrink] → [MemShrink:P2]
|
|
||
Comment 1•12 years ago
|
||
What platforms use the custom linker?
|
Assignee | |
Comment 2•12 years ago
|
||
(In reply to Nicholas Nethercote [:njn] from comment #1)
> What platforms use the custom linker?
Android.
And Linux if you enable it explicitely (used for debugging).
|
|
||
Comment 3•9 years ago
|
||
glandium: this used to block 828844, which suggests that the custom linker uses the system heap. But then you removed that dependency. Which allocator does the custom linker use now?
Flags: needinfo?(mh+mozilla)
|
|
Assignee | |
Comment 4•9 years ago
|
||
(In reply to Nicholas Nethercote [:njn] from comment #3)
> glandium: this used to block 828844, which suggests that the custom linker
> uses the system heap. But then you removed that dependency. Which allocator
> does the custom linker use now?
It uses jemalloc since bug 850332.
Flags: needinfo?(mh+mozilla)
|
|
Assignee | |
Comment 5•4 years ago
|
||
Now that the custom linker a) doesn't do much b) isn't enabled on Android 6.0+, we can do without this.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•