Hello IDE NG,
I'm not sure if this is the correct place to post this message, but wanting to
be helpful anyway ...
About two weeks ago Eclipse update brought a new version of Descent into my
environment
and since then (though I cannot be 100% sure), Descent seems to be frequently
hosing my Eclipse with an
out-of-memory situation occuring. It is possible, of course, that another
plugin is causing the problem.
FWIW, I have captured the Eclipse error log to a text file and some fragments
of evidence are as follows:
!ENTRY org.eclipse.ui 4 0 2009-10-13 00:30:48.797
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.OutOfMemoryError: Java heap space
at descent.internal.compiler.parser.Token.getRawTokenSourceAsString(Token.java:158)
at descent.internal.compiler.parser.Token.toString(Token.java:88)
at descent.internal.compiler.parser.Parser.parsingErrorInsertTokenAfter(Parser.java:8599)
!ENTRY org.eclipse.ui 4 0 2009-10-12 23:02:45.749
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.OutOfMemoryError: Java heap space
at descent.internal.compiler.parser.CompoundStatement.<init>(CompoundStatement.java:19)
at descent.internal.compiler.parser.Parser.newCompoundStatement(Parser.java:9065)
at descent.internal.compiler.parser.Parser.newBlock(Parser.java:8493)
ENTRY descent.ui 4 2 2009-10-12 21:26:53.402
!MESSAGE Problems occurred when invoking code from plug-in: "descent.ui".
!STACK 0
java.lang.NullPointerException
at java.lang.String.<init>(String.java:193)
at descent.core.dom.ASTConverter.convert(ASTConverter.java:3122)
at descent.core.dom.ASTConverter.convert(ASTConverter.java:383)
at descent.core.dom.ASTConverter.convert(ASTConverter.java:3859)
If interested parties would like a copy of my entire Eclipse log to assist
diagnostics & remedy,
please let me know where I can post/email it to.
Cheers
Justin Johansson
The username portion of my email address shown in this NG post is procode

Hello IDE NG,
I'm not sure if this is the correct place to post this message, but wanting to
be helpful anyway ...
About two weeks ago Eclipse update brought a new version of Descent into my
environment
and since then (though I cannot be 100% sure), Descent seems to be frequently
hosing my Eclipse with an
out-of-memory situation occuring. It is possible, of course, that another
plugin is causing the problem.
FWIW, I have captured the Eclipse error log to a text file and some fragments
of evidence are as follows:
!ENTRY org.eclipse.ui 4 0 2009-10-13 00:30:48.797
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.OutOfMemoryError: Java heap space
at descent.internal.compiler.parser.Token.getRawTokenSourceAsString(Token.java:158)
at descent.internal.compiler.parser.Token.toString(Token.java:88)
at descent.internal.compiler.parser.Parser.parsingErrorInsertTokenAfter(Parser.java:8599)
!ENTRY org.eclipse.ui 4 0 2009-10-12 23:02:45.749
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.OutOfMemoryError: Java heap space
at descent.internal.compiler.parser.CompoundStatement.<init>(CompoundStatement.java:19)
at descent.internal.compiler.parser.Parser.newCompoundStatement(Parser.java:9065)
at descent.internal.compiler.parser.Parser.newBlock(Parser.java:8493)
ENTRY descent.ui 4 2 2009-10-12 21:26:53.402
!MESSAGE Problems occurred when invoking code from plug-in: "descent.ui".
!STACK 0
java.lang.NullPointerException
at java.lang.String.<init>(String.java:193)
at descent.core.dom.ASTConverter.convert(ASTConverter.java:3122)
at descent.core.dom.ASTConverter.convert(ASTConverter.java:383)
at descent.core.dom.ASTConverter.convert(ASTConverter.java:3859)
If interested parties would like a copy of my entire Eclipse log to assist
diagnostics & remedy,
please let me know where I can post/email it to.
Cheers
Justin Johansson
The username portion of my email address shown in this NG post is procode

Hi Justin,
This can be a place to post these bugs, another place is the bug-tracker
of Descent:
http://www.dsource.org/projects/descent/newticket
There are two erros: one OutOfMemoryException and one
NullPointerException. For the first one I need to know what project you
have open: is it a big one? Does it happen with a specific module? For
the second I need to know the exact source file, Descent has some
unit-tests but not for every possible combination of character. :-)
(I add tests for bugs as they are found)
Ah, for the first one, if it's a big project it would help me a lot to
open it and see where memory is spent the most. I found a very good way
to diagnose and improve memory performance problems with Java programs.

Hi Justin,
This can be a place to post these bugs, another place is the bug-tracker
of Descent:
http://www.dsource.org/projects/descent/newticket
There are two erros: one OutOfMemoryException and one
NullPointerException. For the first one I need to know what project you
have open: is it a big one? Does it happen with a specific module? For
the second I need to know the exact source file, Descent has some
unit-tests but not for every possible combination of character. :-)
(I add tests for bugs as they are found)
Ah, for the first one, if it's a big project it would help me a lot to
open it and see where memory is spent the most. I found a very good way
to diagnose and improve memory performance problems with Java programs.

Hi Ary,
Thanks for yr response. This morning I pruned my Eclipse environment right down
by especially uninstalling all plugins/features with "wst" in their name.
Since then
not only is Eclipse starting up much faster for me but Descent is seeming much
more
responsive and I haven't witnessed a(n) (Eclipse) crash today.
All in all, I suspect there is an external error that Descent is not dealing
with & this is
causing the problem. This error seems to be a low memory condition caused
perhaps
by other plugins. As you well know, often is the case that one's application
suffers
because of another.
It's probably no point sending you my Eclipse project without sending my entire
Eclipse
environment (which is now pruned right down). Best I keep a vigilant eye and
see what
else turns up in the next few days.
Just in case it helps though, I'm posting my last saved Eclipse error log for
when the crashes
were happening.
Best regards from Australia and thanks for work in bringing D support to
Eclipse.
-- Justin Johansson

Hi Justin,
This can be a place to post these bugs, another place is the bug-tracker
of Descent:
http://www.dsource.org/projects/descent/newticket
There are two erros: one OutOfMemoryException and one
NullPointerException. For the first one I need to know what project you
have open: is it a big one? Does it happen with a specific module? For
the second I need to know the exact source file, Descent has some
unit-tests but not for every possible combination of character. :-)
(I add tests for bugs as they are found)
Ah, for the first one, if it's a big project it would help me a lot to
open it and see where memory is spent the most. I found a very good way
to diagnose and improve memory performance problems with Java programs.

Hi Ary,
Thanks for yr response. This morning I pruned my Eclipse environment right
down
by especially uninstalling all plugins/features with "wst" in their name.
Since then
not only is Eclipse starting up much faster for me but Descent is seeming much
more
responsive and I haven't witnessed a(n) (Eclipse) crash today.
All in all, I suspect there is an external error that Descent is not dealing
with & this is
causing the problem. This error seems to be a low memory condition caused
perhaps
by other plugins. As you well know, often is the case that one's application
suffers
because of another.
It's probably no point sending you my Eclipse project without sending my
entire Eclipse
environment (which is now pruned right down). Best I keep a vigilant eye and
see what
else turns up in the next few days.
Just in case it helps though, I'm posting my last saved Eclipse error log for
when the crashes
were happening.
Best regards from Australia and thanks for work in bringing D support to
Eclipse.
-- Justin Johansson

For the NullPointerException, try updating to a new version of Descent
(I uploaded a new one some days ago due to that exact same bug).