Project

General

Profile

Support #13801

Transient object memory hoarding

Added by Katherine Lato about 4 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Low
Category:
Documentation
Target version:
-
Start date:
09/08/2016
Due date:
% Done:

100%

Estimated time:
Spent time:
Experiment:
-
Co-Assignees:
Duration:

Description

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
using it.
A better solution is to have transient data go out of scope at the end of each event.

History

#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
https://cdcvs.fnal.gov/redmine/projects/larsoft/wiki/LArSoft_Code_Standards#Using-transient-data
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.

#3 Updated by Katherine Lato almost 4 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF