Memory leaks can be difficult to track down. Here are some approaches I might take...
- Identify what process has the memory leak. Use the Windows Task Manager, and sort the processes by memory usage to identify which memory footprint continues to grow over time. It sounds like you have identified it to be open office. - Try to find a way to fix the application or service. There might be a configuration change that can avoid the memory leak. Is there a patch or an upgrade that fixes the memory leak?
- Identify what process has the memory leak. Use the Windows Task Manager, and sort the processes by memory usage to identify which memory footprint continues to grow over time. It sounds like you have identified it to be open office.
- Try to find a way to fix the application or service. There might be a configuration change that can avoid the memory leak. Is there a patch or an upgrade that fixes the memory leak?
Althought these next suggestions do not resolve the memory leak, they can mitigate or manage the leak.
- Schedule a regular restart of that service. If the service consumes too much memory over the course of a week, restarting the problem application every couple days will reset how much memory it is using. - Add more memory to the server. This does not fix a memory leak in any way, but it can delay the impact of the leak.
- Schedule a regular restart of that service. If the service consumes too much memory over the course of a week, restarting the problem application every couple days will reset how much memory it is using.
- Add more memory to the server. This does not fix a memory leak in any way, but it can delay the impact of the leak.
