Re: owstimer.exe using excessive memory

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: jerome_vuibert@xxxxxxxx
Date: Wed, 21 Nov 2007 04:12:02 -0800 (PST)

Here are some news.

After sending about 4Go of dump memory and a lot of phone calls, here
are the results of the analyzis :
- MOSS has a lot of memory leaks. Some of them will be fixed in its
SP1 (release dec. 07 / jan. 08)
- but some memory leaks have not yet been discovered (e.g. mine which
seems to append when the job enumerates UserProfile and make some
operations and commit on them)
- in order to reduce memory leaks problem, be sure that your
environment in Windows Server 2003 with SP2, or later.
.

Follow-Ups:
- Re: owstimer.exe using excessive memory
  - From: jerome_vuibert

Prev by Date: Custom Workflow fails on first run
Next by Date: Re: MOSS 2007 Out of the Box Workflows Broken
Previous by thread: Custom Workflow fails on first run
Next by thread: Re: owstimer.exe using excessive memory
Index(es):
- Date
- Thread

Relevant Pages

Re: Memory Leak detection with HeapAlloc ... ?
... Your code won't detect memory leaks from HeapAlloc because it checks only those allocations taht were made via CRT. ... anyone knows of a solution where one could enable a page heap as described in the articles from sourcecode? ...
(microsoft.public.vc.language)
Re: Memory Leaks?
... > not relinquish all memory back to the available pool for XP to use. ... To flesh this out a bit, memory leaks are a far greater problem in scripts ... When a script terminates, WSH runs a cleanup process that deletes the ... An object will be disconnected only after all references to it ...
(microsoft.public.windowsxp.general)
Re: COM interop between C++ and C#
... But we have detected lot of memory leaks from our side. ... leak detection is notoriously ineffective at preventing false positives. ... There are tools that help a little, but ultimately, short of manually inspecting 100% of your data structures and proving that some block of memory that is still allocated isn't referenced anywhere in your program, it can be hard to know for sure you actually _have_ a memory leak. ... Then these are compared to the known allocations (you also have to override the memory management API, of course, for easiest implementation). ...
(microsoft.public.dotnet.languages.csharp)
Re: Garbage Colletor
... The Large Object Heap isn't compacted ... I'm specifically talking about memory leaks. ... A leak is a bug, but not all bugs are leaks. ...
(microsoft.public.dotnet.languages.csharp)
Re: Memory reclamation under Linux(es) ?
... kernel, though, since you're not complaining about any other app having ... memory leaks. ... ElectricFence that help you find memory leaks in C/C++ programs. ... you're interested in finding/fixing the leaks in Firefox 2, ...
(comp.os.linux.misc)