You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/* XXX: when the app has a ton of mallocs that are quickly freed,
* we spend a lot of time building and tearing down callstacks
* (xref my original setup of not showing leak callstacks by default
* which was for this reason and to save space: but for usability
* it's better to have leak callstacks by default).
* We could just record addresses and not modules, and only on
* module unload or app exit walk the malloc table and fill
* in the module info (and if too many unloads, switch to the
* every-alloc scheme).
*/
From bruen...@google.com on December 01, 2010 09:48:55
/* XXX: when the app has a ton of mallocs that are quickly freed,
* we spend a lot of time building and tearing down callstacks
* (xref my original setup of not showing leak callstacks by default
* which was for this reason and to save space: but for usability
* it's better to have leak callstacks by default).
* We could just record addresses and not modules, and only on
* module unload or app exit walk the malloc table and fill
* in the module info (and if too many unloads, switch to the
* every-alloc scheme).
*/
Original issue: http://code.google.com/p/drmemory/issues/detail?id=75
The text was updated successfully, but these errors were encountered: