whizard is hosted by Hepforge, IPPP Durham

Opened 10 years ago

Closed 10 years ago

#618 closed defect (fixed)

Memory Leak

Reported by: msekulla Owned by: kilian
Priority: P1 Milestone: v2.2.0
Component: core Version: 2.2.0beta
Severity: normal Keywords: memory
Cc:

Description

Whizard has a memory leak when simulating events.

The sindarin file attached will eat your memory!

Attachments (1)

day3_ppttbarlhef.sin​ (454 bytes) - added by msekulla 10 years ago.

Download all attachments as: .zip

Change History (8)

Changed 10 years ago by msekulla

Attachment: day3_ppttbarlhef.sin​ added

comment:1 Changed 10 years ago by msekulla

Summary: Memory Lack → Memory Leak

comment:2 Changed 10 years ago by msekulla

Valgrind is going to be activated on jenkins again for this ticket.

comment:3 Changed 10 years ago by Juergen Reuter

Well, not only for this ticket, but for continuos surveillance :)

comment:4 Changed 10 years ago by Bijan Chokoufe Nejad

The leak disappears when you remove the two unstable statements...

comment:5 Changed 10 years ago by kilian

Priority: P3 → P1
Status: new → assigned

comment:6 Changed 10 years ago by kilian

OK, there are two memory leaks that are relevant here (and were present in all Whizard 2 versions, but didn't harm so much in the old decays code).

The major leak, a broken finalizer in state_matrices, has been fixed in r5558.

There is also a minor leak in interactions. Some problem with pointers here, I'll have to look more closely.

There are (many) other leaks that nagfor -mtrace reveals. I'll try to fix them, but they are harmless if they do not occur during integration/event generation. New ticket #623.

comment:7 Changed 10 years ago by kilian

Resolution: → fixed
Status: assigned → closed

The second leak is also gone (r5559). Otherwise, cf. #623.

Note: See TracTickets for help on using tickets.