Bug #6642
Memory leaks in FLAME algorithm
Status:
Closed
Priority:
Normal
Assignee:
Category:
Reconstruction
Target version:
Start date:
07/18/2014
Due date:
% Done:
100%
Estimated time:
Occurs In:
Experiment:
MicroBooNE
Co-Assignees:
Description
The new FLAME algorithm in fuzzyCluster module in larreco v02_02_01 presents some memory leaks (I have not quantified the size).
The code is C and allocates memory using C memory allocation functions.
Restructuring the code in C++ is not hard given the existing structure, and it is recommended to avoid leaks.
History
#1 Updated by Gianluca Petrillo over 6 years ago
- Occurs In v02_02_01 added
- Occurs In deleted (
x_future_release)
#2 Updated by Lynn Garren over 6 years ago
- Status changed from New to Assigned
- Assignee set to Ben Carls
#3 Updated by Gianluca Petrillo over 6 years ago
Note: this is related to the issue #6452.
#4 Updated by Lynn Garren over 6 years ago
- Assignee changed from Ben Carls to Gianluca Petrillo
Ben has committed a change, but Gianluca should check the changes.
#5 Updated by Gianluca Petrillo over 6 years ago
- Category set to Reconstruction
- Status changed from Assigned to Resolved
- Target version set to v02_05_01
- % Done changed from 0 to 100
- Occurs In v02_03_01 added
- Occurs In deleted (
v02_02_01) - Experiment MicroBooNE added
- Experiment deleted (
-)
The new C++ structure prevents leaks by construction, and I could not spot any issue with it.
#6 Updated by Gianluca Petrillo over 6 years ago
- Status changed from Resolved to Closed