|
![](/i/fill.gif) |
Darren New wrote:
> Orchid XP v8 wrote:
>> Generally that kind of thing isn't so bad though. All the garbage that
>> gets paged out never gets paged back in again.
>
> Sometimes when you kill a big process, it actually does have to read
> everything back in, to run finalizers or whatever, and to generally
> deallocate memory. It's not unusual to hit ctrl-C on a CLI-driven
> program and have it take a minute or more to exit even if you're not
> catching signals.
I haven't seen that problem with programs I've written myself (which
obviously don't use finalisers), but I've seen other software do this...
Post a reply to this message
|
![](/i/fill.gif) |