Hi Allan, > the very last line of code in the On Server Shutdown message is a logging > entry, which DOES get executed so we no it's not getting hung up on code in > there.
Perhaps the application is releasing the memory? Take a look at the Task Manager and watch the memory for the 4D Server.exe process after you choose QUIT. Essentially the memory value of the process decreases until it reaches 0 and then the application finally quits. The release of memory was sometimes slower in large application with very large cache sizes running with some of the v17.x-v17R releases. Good news, with optimizations in v18 this process of quitting seems to be about 10x times faster - For example: - With a cache having 28GB of data - With 4D 17 R5 Time to quit : 3m 20s - With 4D v18 and the new optimization. Time to quit : 16 seconds. If this is what you are seeing I would suggest either waiting until the process completes on its own or upgrading to v18 to get the optimization, bottom line is to avoid using the "End Task" feature if at all possible. -Tim ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
