Keep(s) on running

[Rene Simons]

Hi,

I sometimes happens that the application keeps running (according to the task manager) after I close the app. I only notice this when I recompile and the obvious error message appears.
Is anyone familiar with this?

Rene

[Wolfgang Orth]

Hello Rene,

yes, I see that some times also. I think, in each case it was my fault. Mostly by adding some code which causes my program to crash, but after it has been loaded. After closing it, it did not get renmoved from memory.

No idea, who is to blame (except me for the faulty code <g>).

Whishing to a bug-free week,
Wolfgang

[Bruce]

Hi Rene,

This can happen if the program crashes of course. But assuming the program hasn't crashed, it's usually because a thread is still running. This usually happens in one of two situations;

a) one of your response-threads (remember each request starts a response thread) hasn't ended. This might be because it's generating a report, or in some tight-loop of code or something like that. or

b) the nettalk comms thread is not closing. You can do this on purpose via the template settings, but given your description as "sometimes" I'm guessing it's more likely to be issue a)

cheers
Bruce

[kevin plummer]

b) the nettalk comms thread is not closing.

> which\where template setting could I check this?

[Rene Simons]

Thanks Wolfgang/Bruce.
Good question Kevin.

Rene

[Bruce]

as long as nettalk is in your exe app there's nothing you need to do.

You can _suppress_ the behaviour in your exe by ticking on the option on the nettalk global extension, advanced tab. But that's only there for DLL's which are linked at _runtime_.

If this was the problem, the app would never close correctly.

cheers
Bruce