Re: Memory Issue

Jason.Herald@xxxxxxxxx wrote:


I will post more passes (fyi the number is the current available
memory so it is going to go down).

If I let the app run for 20 minutes it runs out of memory.

And no there are no errors aside from the java.lang.OutofMemory

Well at least 20 minutes is relatively quickly. Unfortunately after you attach a debugger 20 minutes might turn into 20,000 minutes. I think you'll need to try anyway. Get a debugger or other performance tool, attach it and let the process run. Collect GC info so you can see what objects are surviving GC. (They'll have their generation number increasing.) That should at least get you pointed at the right part of the code.

Here's an older reference, I didn't have time to look extensively for the latest info:

<http://www.ibm.com/developerworks/library/j-perf06304/>

It will at least get you some key words to search for and get a debugger running in your environment. I think that's the first step. Until you have some clue where the error really is, posting code is unlikely to produce a resolution. And knowing how to attach tools and profile your code is a useful skill.
.

Relevant Pages

  • RE: Memory growth halts with use of Profiler - bug in .NET services?
    ... unless I attach a debugger to it. ... application instead of as a service, I have no memory problems at all. ... I'll try the SOS debugger and also the CLRProfiler, ... This is basically the manual version of what CLRProfiler does; ...
    (microsoft.public.dotnet.framework.performance)
  • System Idle Process
    ... According to TaskManager, this process uses some memory (seem to be ... It is not possible to attach a debugger to ...
    (microsoft.public.win32.programmer.kernel)
  • Re[4]: Protecting code and data in Windows
    ... DE> How about using something like VirtualProtectExand set the memory storing ... This approach could be interesting to "protect" from malicious code ... So the first problem to soluce will be to avoid such a debugger ... to attach to our critical process. ...
    (SecProg)
  • Re: MyString Class
    ... > I compiled your program and run it under the debugger. ... > The first crash happens in ... ... > memory is flawed. ... First bug fixed. ...
    (comp.lang.cpp)
  • RE: Memory increasing even when in debug-break
    ... there are 2 types of memory leak in .Net: ... More interesting is the debugger breaks while memory still increasing ... Microsoft Online Community Support ...
    (microsoft.public.vsnet.debugging)