156764 2016-04-19 15:35:13 -0700 Consider gathering backtraces at allocation sites to show in the web inspector 2017-01-18 23:39:06 -0800 1 1 1 Unclassified WebKit JavaScriptCore WebKit Nightly Build Unspecified Unspecified NEW InRadar P2 Normal --- 1 saam saam benjamin darin emacemac7 fpizlo ggaren gskachkov joepeck keith_miller mark.lam msaboff nvasilyev oliver sukolsak webkit-bug-importer ysuzuki oldest_to_newest 1185190 0 saam 2016-04-19 15:35:13 -0700 A possible implementation could be done purely at the byte code level. Store a private property on the object that was just allocated which contains whatever meta information you want. It could be a backtrace. It could be a code location. 1185196 1 oliver 2016-04-19 15:39:56 -0700 Maybe we could even just limit it to larger (for some clarification of what that means) allocations so it could be almost(?) always-on? 1185333 2 saam 2016-04-19 21:33:48 -0700 (In reply to comment #1) > Maybe we could even just limit it to larger (for some clarification of what > that means) allocations so it could be almost(?) always-on? I'm not sure how you could easily do such a thing easily. Object size grows as the object lives longer. I guess you could have some kind of a system that starts by profiling everything and then backs off slowly to only profile some things as it figures out the tendency of the program's allocations. That seems hard and I'm not even sure it would work. Were you thinking of a particular mechanism when you suggested this? 1188454 3 webkit-bug-importer 2016-04-28 17:20:33 -0700 <rdar://problem/25994092>