Re: Basic program with tasks goes out of memory

[wojtek@power.com.pl (Wojtek Narczynski)]

"Jean-Pierre Rosen" <rosen@adalog.fr> wrote in message 

>> So instead of a single delay you may prefer
>>
>> -- Inner loop:
>> loop
>>     if Dummy'Terminated then
>>        Free (Dummy);
>>        exit;
>>     else
>>        delay 0.01; -- To not hog CPU
>>     end if;
>> end loop;

> If (like me) you don't like busy waiting, you can do the following:
> begin
>    Dummy.Never_Accepted;
> exception
>    when Tasking_Error =>
>       null;
> end;

Yes, if Free (Dummy) is called when the task is not yet terminated,
the program still leaks. I can see that behaviour on an isolated
testcase, but not in my actual code, which probably leaks too slowly.

But in the actual code the idea is to have one task per connection,
which can mean hundreds of tasks. Their time to terminate can be very
different. I don't see how this idea could be extended to hundreds of
tasks. Jano's idea could, but only with polling.

Regards,
Wojtek