Treat [stack:nnnn] entries in /proc/self/maps as anonymous memory

RESOLVED FIXED in mozilla21

Status

()

Core
XPCOM
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: njn, Assigned: njn)

Tracking

(Blocks: 1 bug)

Trunk
mozilla21
All
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [MemShrink])

Attachments

(1 attachment)

(Assignee)

Description

5 years ago
Bug 819769 comment 11 explained that [stack:nnnn] entries are best treated like anonymous memory.
(Assignee)

Updated

5 years ago
Hardware: x86_64 → All
Whiteboard: [MemShrink]
(Assignee)

Comment 1

5 years ago
Created attachment 701674 [details] [diff] [review]
Treat [stack:nnnn] entries in /proc/self/maps as anonymous memory.

Simple.
Attachment #701674 - Flags: review?(justin.lebar+bug)
Comment on attachment 701674 [details] [diff] [review]
Treat [stack:nnnn] entries in /proc/self/maps as anonymous memory.

My kingdom for nsAString::StartsWith.
Attachment #701674 - Flags: review?(justin.lebar+bug) → review+

Comment 3

5 years ago
http://mxr.mozilla.org/mozilla-central/source/xpcom/glue/nsStringAPI.h#1370

One kingdom, please.
Do I get out of this on the technicality that it's not a method on nsAString?  :)
(Assignee)

Comment 5

5 years ago
https://hg.mozilla.org/integration/mozilla-inbound/rev/ffef8f23abd4

Comment 6

5 years ago
https://hg.mozilla.org/mozilla-central/rev/ffef8f23abd4
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla21
You need to log in before you can comment on or make changes to this bug.