We call QUIT 4D directly with no timer. Our On Exit and On Server Shutdown methods already do checks to be sure the processes we started are dead.
I’m hoping for sure this is all that is needed. I didn’t think to test if this was only an issue related to 64bit version of server on Mac. I’ll have to give that a shot as well. Regardless, at the moment at least, starting a new Stored Procedure to run the startup code seems to have done the trick for me. I’ll test 32bit server on Mac later today. Have some other TS issues to catch up on first. Randy ---------------------------------------------------------------------- Randy Jaynes Senior Programmer and Customer Support http://printpoint.com <http://printpoint.com/> • 845.687.3741 • PrintPoint, Inc • 57 Ludlow Lane • Palisades, NY 10964 Please send all email contacts to supp...@printpoint.com <mailto:supp...@printpoint.com> > On Aug 6, 2018, at 10:54 AM, John DeSoi via 4D_Tech <4d_tech@lists.4d.com > <mailto:4d_tech@lists.4d.com>> wrote: > > Randy, > > I'll be interested to hear if this permanently fixes the problem. I'm still > having random crash on quit errors on 4D Server (16.3HF4, 64-bit). Never a > problem in version 15, 32-bit. I have never connected crashing to a status > interface, but in my case it has always run in a separate process. I just > made a change to ensure that process is dead before QUIT 4D is called on the > server. Maybe that will completely solve it. > > Did you look at the backtrace from the crash log? I would be interested to > see if we are experiencing the same issue. Below is what I see. I wonder if > that is related to displaying the countdown timer - I'm quitting with QUIT > 4D(60). ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
