🚀 go-pugleaf

Hi all. 

I have a background thread writing a (selective) log of user 
activity to a table for audit purposes. On occasion this will
receive a significant number of entries just before the app 
terminates (the user goes "yup, save all of those, I'm done").

At this stage the UserLog unit creates/starts and frees the
thread in the initialization/finalization sections, but
this causes AV's if the thread is active when the app 
terminates - it looks as if the memory used is free'd from 
underneath the thread.

Questions:
1: does code in the finalization block actually have to
   complete before the app shuts down? I've assumed so.
2: It looks as if the app does not wait for my thread to 
   terminate. Correct?

What's the best way around this?
- terminate the thread then write any remaining entries from
  the main thread.
- do that but using the database and query owned by the thread
- sit in a loop polling the buffer until it's empty, then 
  exit the finalization block?
- do something else. Any ideas?

The other thing I've thought of doing in making the thread 
depend on the main form - put the start/stop into the form
create/free. Does this sound reasonable?

Thanks
Moz