On Mon, May 17, 2010 at 12:43 PM, June Xue <[email protected]> wrote: > Hi Guys and Girls, > > Is it true that only memory leak can cause OutOfMemoryException errors? Is > it possible that one application uses too much memory so that > OutOfMemoryException errors occur in the other applications in the > same application pool?
Sure indeed it can, because an application pool is (IIS6.0: http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/67e39bd8-317e-4cf6-b675-6431d4425248.mspx?mfr=true) Seems reasonable to consider that yes, if two things are assigned a given amount of memory then either one can use it all and cause the other to crash. As to your earlier statement; it's probably a bit vague. You can create an OutOfMemoryException - presumably - by trying to create too many objects. Is that a "leak"? No. But that said, if your application runs "fine" normally and dies after only a long running time, then yes, it's probably a leak. If it dies during high loads, then probably some process does "too much" at once, and is getting executed too many times (more than you can handle). In that case, you'd want to allocate more memory, and somehow throttle the traffic before it reaches that critical point. > Thanks in advance! > > June -- silky http://www.programmingbranch.com/
