Transient object memory hoarding
Data structures that contain transient data and that remain in scope at the end of the
event should be cleared at the end of the event rather than at the beginning of the next event. The
LArSoft team should investigate how often this pattern occurs, and educate users in the perils of
A better solution is to have transient data go out of scope at the end of each event.
#1 Updated by Katherine Lato almost 4 years ago
- Status changed from New to Assigned
- Assignee set to Gianluca Petrillo
- Priority changed from Normal to Low
To make progress, we're going to ignore the 'investigate' and focus on the educating users. Starting by having a 'good code example' on
that will show having transient data go out of scope at the end of each event.
#2 Updated by Gianluca Petrillo almost 4 years ago
- Category set to Documentation
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100
LArSoft wiki page https://cdcvs.fnal.gov/redmine/projects/larsoft/wiki/The_rules_and_guidelines was updated with an extensive example.