Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] OutOfMemory debugging in Eclipse

Thank you! I had also found the Memory Analayzer Tool at

2008/10/8 Thomas Ball <tball@xxxxxxxxxx>:
> Try running with the Java 6 -XX:+HeapDumpOnOutOfMemoryError flag,
> which creates a dump that jhat (part of JDK 6) can probe.  Here are
> the details:
> Tom
> On Wed, Oct 8, 2008 at 9:44 AM, Dmitry Smirnov <divis1969@xxxxxxxxx> wrote:
>> Hi,
>> I'm using AST to parse files of the big project. Once parsed, some
>> info is extracted from translation unit and stored in
>> org.w3c.dom.Document.
>> When I first encountered the OutOfMemoryError, I suspected this
>> Document to become very large. So, I've changed the way I use it and
>> discard all the additons once they are not needed.
>> But the OutOfMemoryError still persist! Perhaps I'm not releasing
>> something, but I cannot figure out that...
>> So, I would like to ask you, is there any way to debug this problem?
>> Can I know what is the memory status (i.e. how much is occupied, how
>> much is total)? I'm running my application as an application, not a
>> product, so I suppose the numbers in status line of Eclipse IDE is the
>> memory heap of this IDE process).
>> Can I find somehow any "huge" objects in heap?
>> P.S. Obviously, this maillist is not for this question, but maybe you can help.
>> Dmitry
>> _______________________________________________
>> cdt-dev mailing list
>> cdt-dev@xxxxxxxxxxx
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx

Back to the top