I think this is directed at EP, but maybe someone else knows what I'm talking about and has a workaround.
If I bring up my TWX/Swath combo and do something online quick and get right back off, I seem to have no issues.  When I bring up that combo and stay online for hours, when I try to shut down I get errors from TWX and it won't close.  I have to go into the task manager and shut it down.  This always leaves me wondering what the condition of the database is when I have to force it to terminate this way.
Why is this happening, how to I fix it, and is the database ok when I force termination like that?  This has gotten rather annoying to me.  I've not tried the ZOC/twx to see if it does the same.
 
 
 

Zoc/TWX has a moment like that once in a while too... but, I've had no issues with the database being corrupted. It always seems ok when I open back up.

As yet, this bug still hasn't been squished. I hope to have more time for coding in the near future, and will tackle it then.

..wondering if it's somehow related to Data in Memory that's not getting committed to the DBase, or is getting saved but progeam ends too fast.
I'm gessing this because when I load up TWX and select a game that's not already displayed in the combo-box, and TWX ends with the error, I will have to reselect the game at next load (as opposed to when TWX doesn't error out upon termination; in which case TWX 'remembers' the last game played.)
P.S. same thing occurs with all TWX settings, not just the Combo-box game selector thingy.

Remco used a complex module factory that builds and loads the various modules that make up TWX at load time, then iterates through them and destroys them when TWX exits. This is where the exception occurs during exit, and it is evidently occurring at a point earlier than when the Persistence module saves the session settings. I have not heard of a single instance where this crash on exit causes a database problem.

A memory leak is something else entirely.