|
From: Philippe W. <phi...@sk...> - 2009-05-21 23:11:25
|
> So, at least in terms of stack trace size, I imagine that a callstack of JCC for each > allocation should work. (using an hash table to share the identical JCC callstacks to > avoid duplication). I have now implemented this solution (but using an OSetGen of jCC callstack rather than an hash table). Testing this on firefox startup gives reasonable result: there is about 72000 different jCC stack traces, 4,000,000 elements in these stack traces. => so, on a x86, this needs about 20Mb of memory I still have a few things to cleanup/improve. I will then send the current state of the code as a basis to discuss/review (there are for sure points to improve/change/enhance/...) Philippe |