trunk/52ba1c3557bddebc9cdacb3a09e2337bf518ec7d: Report every mapped segment in a per-pool memory snapshot (#199845)
- PyTorch: 1956 events in the last 90 days
- PyTorch: 1930th Release in the last 90 days
- Previous: earlier the same day · trunk/4ea41f67cf8f9bab17ac1d56485c4d8426c65767
What happened
Summary (human written only) Human note: fix memory_snapshot not reporting valid segments if they come after an unmapped hole. This doesn't happen in normal growth scenarios (there are no unmapped holes) but release_blocks called during empty_cache can lead to this situation Agent details (if applicable) memory_snapshot(mempool_id=...) dropped part of any expandable segment with an unmapped hole. The snapshot report…
Summary assembled by rule from the sources below