Hi, I just landed the patch from https://bugzilla.mozilla.org/show_bug.cgi?id=1134030 which adds a new memory reporter for the Windows address space. Sample output:
> 2,147,418,112 B (100.0%) -- address-space > +--1,662,676,992 B (77.43%) -- free [229] > +----299,868,160 B (13.96%) -- commit > | +--142,098,432 B (06.62%) -- image > | | +---94,035,968 B (04.38%) -- execute-read [107] > | | +---44,826,624 B (02.09%) -- readonly [245] > | | +----1,736,704 B (00.08%) -- writecopy [62] > | | +----1,499,136 B (00.07%) -- readwrite [151] > | +--127,987,712 B (05.96%) -- private > | | +--122,867,712 B (05.72%) -- readwrite [224] > | | +----2,977,792 B (00.14%) -- readwrite (stack) [128] > | | +----1,310,720 B (00.06%) -- readwrite+guard [128] > | | +------729,088 B (00.03%) -- execute-readwrite [13] > | | +-------53,248 B (00.00%) -- execute-read [11] > | | +-------49,152 B (00.00%) -- readonly [12] > | +---29,782,016 B (01.39%) -- mapped > | +--18,513,920 B (00.86%) -- readwrite [31] > | +--11,268,096 B (00.52%) -- readonly [25] > +----184,872,960 B (08.61%) -- reserved > +--161,124,352 B (07.50%) -- private [177] > +---23,474,176 B (01.09%) -- mapped [5] > +------274,432 B (00.01%) -- image [6] The numbers in square brackets indicate how many distinct memory regions had each particular set of characteristics. We've had increasing numbers of cases lately on Windows where memory usage goes out of control but the existing memory reporters (e.g. the "explicit" tree in about:memory) doesn't show anything. This is because the memory usage is related to gfx and/or video playing and so comes from the graphics driver or something similar. This new reporter is an attempt to get some insight into such cases, though it's still fairly crude. If anybody else has any ideas on additional measurements that could prove helpful for these kinds of cases, please let me know. Thank you. Nick _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
