Re: Delayed deallocation of non-terminated task in Gnat?

[Simon Wright <simon@pushface.org>]

Robert A Duff <bobduff@shell01.TheWorld.com> writes:

> You can loop, checking 'Terminated, with a delay.  But the delay is
> guaranteed to be either too long or too short -- most likely both.
> The feature we're talking about was implemented because there was such
> a loop, and it was causing an AdaCore customer's program (with
> thousands of dynamically allocated tasks) to take half an hour.  After
> implementing this feature, and removing the loop-with-delay, it took a
> few seconds.

We couldn't afford to wait, so once we discovered the leak we arranged
that all tasks to be deleted were aborted and placed on a special list;
a low-priority task did the loop-with-delay-until-terminated and then
the U_D.

   generic
      type Task_Type (<>) is limited private;
      --  The class's task type (T).
      type Task_Type_P is access Task_Type;
      --  The class's pointer-to-task (T_P).
      with function Is_Terminated (It : Task_Type_P) return Boolean;
      --  We can't say that Task_Type is actually a task, so we can't use
      --  'Identity.
   package ColdFrame.Task_Deletion_G is
      procedure Free (It : Task_Type_P);
      --  Puts It on the queue of tasks to be freed.
   private

(a) all the instantiations and calls of this code were autogenerated, so
the developer pain was minimised; 

(b) we didn't have many task deletions (mainly on network disconnects).