(Check yer mail)
Previous to what? Don't know if this current version produced a runtime error on forfeits on other setups. This is the first I have observed this build running on SQL with any significant number of live players. If we could do a stock test and reproduce the result, that would be handy. (it might be the shiplist/settings of course.)
BUT, consistently, all builds of the kit on SQL since EAW 2036 spike the processor hideously on forfeits, handles are not released, and threads do not die, it starts the memory leak process then the kit/server eventually die. Down with forfeits!
It does not necessarily start the death throes with every forfeit, but depending on coincidence of events and CPU use, if the processor is spiked to 100% for longer than a few seconds the death throes usually start, but interestingly it is improved on this build, it still leaks memory but not as badly, and handles are released, it generates a runtime error and keeps running until the error is acknowledged. So something has changed for the better. Previous builds did not generate a runtime error, but just died or hung.
Of course we need to fix them, or make it so the kit does nothing, or something more apropriate when the button is pressed, if possible. A player forfeiting a mission they drew themselves should not be too complicated to rectify, but a player forfeiting a draft is the more complicated case... is it using the same code for both events? We need to examine this in detail.