Open GoogleCodeExporter opened 9 years ago
FWIW: I believe some (maybe all) of the referenced errors occur when the
server is Active when the TIdSchedulerOfThreadPool is attempted to be free'd.
Workaround for AV's in a new server just thrown together was to simply ensure
server.Active := False before freeing the assigned TIdSchedulerOfThreadPool.
Original comment by dar...@darianmiller.com
on 1 Jul 2013 at 9:56
Original issue reported on code.google.com by
gambit47
on 24 Nov 2009 at 1:25