Closed Bug 71712 Opened 24 years ago Closed 8 years ago

use linker ordering fu to evaluate resident set

Categories

(Firefox Build System :: General, defect)

Product:
Firefox Build System
Component:
General
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: waterson, Unassigned)

References

Details

(Keywords: helpwanted, memory-footprint)

It should be possible to use a linker ordering script to place each symbol in a DLL on its own page. Once that's done, it should be much easier to assess the resident set of mozilla/gtkEmbed. So, this bug means: 1) Figure out how to make the linker put each symbol on its own page, possibly on a per-module basis 2) Evaluate resident set after doing so to see which symbols are being touched.
Status: NEW → ASSIGNED
Keywords: footprint
Priority: -- → P3
Target Milestone: --- → mozilla0.9
Blocks: 71874
End-of-milestone reality check.
Target Milestone: mozilla0.9 → mozilla0.9.1
Keywords: helpwanted
Target Milestone: mozilla0.9.1 → Future
Product: Browser → Seamonkey
Assignee: waterson → nobody
Status: ASSIGNED → NEW
Component: General → Build Config
Priority: P3 → --
Product: Mozilla Application Suite → Core
QA Contact: doronr → build-config
Target Milestone: Future → ---
This seemed like an interesting idea at the time. But I'm guessing our memory measurement story has changed sufficiently in 16 years and this is no longer wanted.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.