Yes, that's what I'd assume too. The problem *looks* like a memory leak
yet only affects one particular site which is why it's so strange. I did
some Googling but came up with little. The only other suspects I found
were related to information being passed to a COM object, and possibly
if you'r
Armando,
I appreciate the response. Hopefully we can track it down better. The
websites which are functioning properly are actually much more complex than
this one. lol.
The only real difference is that I have some javascript running a countdown
clock which is displayed using images which are
If it goes away on a server reboot for a period of time, then it sounds
suspiciously like a memory leak, ie; the application is trying to
reference an area of memory it doesn't have access to. I've seen this
problem with other applications... they'd run fine for a period of time
after a reboot
