Closed Bug 677704 Opened 15 years ago Closed 15 years ago

Implement memory reporters for nsWindowsDllInterceptor

Categories

(Core :: XPCOM, defect)

Product:
Core
Component:
XPCOM
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: ehsan.akhgari, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [MemShrink])

Each nsWindowsDllInterceptor allocates a page of virtual memory for its trampoline code. Should we implement memory reporters for this class?
Blocks: DarkMatter
> Should we implement memory reporters for this class? That depends how much memory is used. Can you do an ad hoc measurement to get an idea?
There are 4 WindowsDllInterceptor instances, so we're probably looking at 16K. We could have a singleton to share a page between all the instances, but is it worth the bother?
16KB? Not worth bothering with. Using data from DMD to decide which reporters to implement is the best way forward, IMO.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.