Re: RDP 8.5.1. --> An internal error occurred during: "RPG ParserScheduler for XXXXXXXXXX.SQLRPGLE

That appears to go back to the RDP V8.5.1 eating memory thread. Last Friday (or was it Thursday...I'm losing track of time) I noticed my heap suddenly ballooned to over 900K nearing that 1024K cap, and all I did was open a few members and I believe run a search. I'm not sure what caused it to do that because I wasn't paying attention to it, then suddenly noted it. As these are new PCs we have with 4G memory, it wasn't noticeable in terms of performance. Something appears to have broken. Today in opening a few members and running Debug, it hasn't cracked 250K yet. But I'm starting to pay closer attention to it.

If I recall right, there is some tracing that can be turned on to track this...I'll have to look at this later as time permits because it might yield useful information for IBM to work on.


-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Ken Killian
Sent: Monday, January 14, 2013 11:44 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: [WDSCI-L] RDP 8.5.1. --> An internal error occurred during: "RPG ParserScheduler for XXXXXXXXXX.SQLRPGLE

Hi,

I am using RDP 8.5.1, and editing SQLRPGLE code, and the response time was TERRIBLE...

It finally blew up on this error:
An internal error occurred during: "RPG ParserScheduler for XXXXXXXX.SQLRPGLE".
Java heap space

Where XXXXXXXXXX is the program name.

Exception Stack Trace:
java.lang.OutOfMemoryError: Java heap space
at lpg.runtime.Stacks.allocateOtherStacks(Unknown Source)
at lpg.runtime.BacktrackingParser.parseActions(Unknown Source)
at lpg.runtime.BacktrackingParser.fuzzyParseEntry(Unknown Source)
at lpg.runtime.BacktrackingParser.fuzzyParse(Unknown Source)
at com.ibm.etools.iseries.rpgle.parser.RPGParser.parser(Unknown Source)
at com.ibm.etools.iseries.rpgle.parser.RPGParseController.parse(Unknown Source)
at org.eclipse.imp.editor.ParserScheduler.run(Unknown Source)
at org.eclipse.core.internal.jobs.Worker.run(Unknown Source)

Notice memory was 1019 out of 1024 the "Little Trash Can" to show the "heap Status".
Windows>preferences>General --> Check box(checked) show heap status)

As usual, a restart seems to clear it...
<sigh>

First time I happen to see this error, trying to pay attention to error, instead of ignore them and restarting...

-Ken Killian-