ColdFrame / Bugs / #48 Memory leak

#48 Memory leak

Status: closed

Owner: Simon Wright

Labels: Generation (37)

Priority: 5

Updated: 2012-09-24

Created: 2008-07-03

Creator: Simon Wright

Private: No

When an active instance is deleted, no check is made for whether
its task has actually terminated. If it hasn't, the task won't
actually get deleted, and memory will leak.

ColdFrame #0371.

Discussion

Simon Wright - 2008-07-08

Logged In: YES
user_id=917025
Originator: YES

This change requires regeneration (the ColdFrame library/project code has changed).

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Simon Wright - 2011-01-04

The problem can only be fixed by altering the code generation strategy; on deletion of an instance of an active class, the task is placed on a special list after aborting it, and a separate low-priority task does the actual deletion when the task is terminated.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Simon Wright - 2011-01-05

Accidentally re-opened while improving comments.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Memory leak

Group

Searches

Help

#48 Memory leak

Discussion