Wilfried Mestdagh wrote: > Hello Angus, > > there was another one (forgot wich one). you need to see how many in > use for non-paged memory (used by socket and overlapped IO).
Won't that be just workarounds? I guess either sockets are not closed properly or someone tried a DoS. In the latter case even sockets in state WAIT_TIMEOUT count, and unfortunately you cannot prevent those WAIT_TIMEOUT sockets when you initiate connection close. If so, stop listening for a while when a DoS is detected. -- Arno Garrels > > --- > Rgds, Wilfried [TeamICS] > http://www.overbyte.be/eng/overbyte/teamics.html > http://www.mestdagh.biz > > Saturday, December 15, 2007, 19:16, Angus Robertson - Magenta Systems > Ltd wrote: > >>> I recall it is winapi call GlobalMemoryStatus > >> I check GetProcessMemoryInfo and GlobalMemoryStatus every 30 seconds >> in another application, but it was not running on the PC that lost >> TCP today, which has 3 gigs of RAM. This logging is from a couple >> of days ago, if the memory load reaches 98% or free virtual drops >> below 200 megs, the PC is rebooted. > >> Monitor Memory: Working Set 15.4M; Paging File 9.34M; Address Space >> 3.75M; Heap Allocated 582K; Free 3.14M >> Global Memory: Load 33%; Total Phys 2.00G; Free 2.00G; Total Paging >> 4.00G; Free 4.00G; Total Virt 2.00G; Free 1.93G > >> Actually, the global free figures above look very suspicious, this >> would have been Delphi running the application under the debugger on >> XP Pro, and it must have been using some memory! Maybe the API can >> not cope with more than 2 gigs of physical memory. > >> Angus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
