Closed Bug 560970 Opened 15 years ago Closed 8 years ago

investigate making critical sections of xul.dll not pageable

Categories

(Firefox Build System :: General, defect)

x86
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: blassey, Unassigned)

Details

(Whiteboard: [ts])

Notes, nopageable locks the mmap in memory. Preload is an interesting flag, would be nice to know what that does.
OS: Linux → Windows 7
Nonpageable memory is generally considered bad sportsmanship. What are the "critical" sections of xul.dll? I would be interested to see if we could segregate little-used code, e.g. accessibility or xslt code, if we could demonstrate that most users will *never* load that code and we can avoid loading it at all. But I'm a little skeptical that given the breadth of our code, marking some pages as nonpageable will actually improve things if the OS gets into a state where it decides it wants to page Firefox.
Mass bug cleanup for Core:Build Config. If you feel this bug has been closed in error, please re-open with new details.
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.