Lines Matching full:death
19 // that are tracked. Tracking means their birth, death, duration, birth thread,
20 // death thread, and birth place are recorded. This data is carefully spread
82 // death count, as well as accumulate the lifetime duration of the instance as
101 // threads that have recorded a birth or a death, we create a singly linked list
117 // be able to run concurrently with ongoing augmentation of the birth and death
123 // birth thread, death thread, and location, along with the count of such
127 // birth and death datastructures, but have local (frozen) copies of the actual
158 // death info (with tallies for each death thread, to prevent access conflicts).
218 // a corrosponding death.
254 // When snapshotting a full life cycle set (birth-to-death), use this:
258 // When snapshotting a birth, with no death yet, use this:
306 // After collection of death data is complete, we can add entries for all the
323 // seen a death count.
495 // Find a place to record a death on this thread.
512 // Hack: asynchronously clear all birth counts and death tallies data values
518 // Using our lock to protect the iteration, Clear all birth and death data.
604 // Similar to birth_map_, this records informations about death of tracked
