Skip to content

Memory leaking in Contributor

Having problems with your dllhost.exe grabing a huge amount of RAM and going into winter sleep? A real hog he is, that dllhost.exe.

CenterStone pointed on Cognoise, that COM+ memory leaking is an accepted Planning bug, and is resolved in 8.1.
Well, I didn’t know that, so had to deal with this problem in 7.3 SP3. Here are the recipes I gathered.
Problem
“Planning73″ Com+ component leaks memory and that leads to server hang up, due to overfilling of dllhost.exe
Solutions

  1. Recycling parameters that set up the condition for COM+ restarting a copy of component and redirecting all connections to it, while stopping the instance that reached some parameter(RecycleMemoryLimit in my case). See msdn article for details. This can be set on XP and 2003, couldn’t find that option on 2000.
  2. If 1 is not applicable, regular COM+ restarts should help as well. See previous post for COM+ restarting script.
  3. A vile and mean way of killing dllhost.exe, after it reached some limit. That is done easily, as noted here, for example. That can lead to some trouble, though, for example if dllhost is killed in the middle of reconcile process.

I use 1&3 for reliability.

  • Pingback: Cognos EP log analysis | ykud

  • DesiCresnet

    Memory leak is still exist as of 8.3. This time this is in Content manager. When the jave.exe outgrows and you get CAM-AAA-0071 “An internal error occurred”. There are other reasons you get this. But if you look at the CM boxes and logs you can clearly find out java.exe memory leak issue. After a CM hotfix and a HeapDecommitFreeBlockThreshold setting regisrty we put an end month over prod unstability.

  • DesiCresnet

    More details on HeapDecommitFreeBlockThreshold at http://support.microsoft.com/kb/315407

  • ykud

    Yes, I’ve seen this on 8.3 instances, but didn’t know about HeapDecommitFreeBlockThreshold setting. Thank you very much, it’s incredibly valuable.
    Can you share details on CM hotfix (number and all) — just to ease up requesting it from Support?

    I think I’ll put up a separate post on this topic. As far as I see, it’s a very common 8.3 problem.