Bug 14755 – Could -profile=gc also give the number of allocations that led to X bytes being allocated?
Status
RESOLVED
Resolution
FIXED
Severity
enhancement
Priority
P1
Component
dmd
Product
D
Version
D2
Platform
All
OS
Windows
Creation time
2015-07-01T13:48:00Z
Last change time
2015-10-04T18:19:15Z
Keywords
pull
Assigned to
nobody
Creator
aliloko
Comments
Comment #0 by aliloko — 2015-07-01T13:48:45Z
Currently -profile=gc gives a list of top GC spots sorted by bytes (and that is already useful). Could we also get the corresponding count of GC allocations along with that number?
Rationale: not all memory is scanned and a frequent allocation of objects with references worries me more than a big uint[] that happen only once.
Comment #1 by dlang-bugzilla — 2015-08-31T11:16:52Z