Show of hands, how many of you have upgraded to version 2.2.1 of BIRT? Okay, now how many of you have had memory issues? Based on my experience and the messages on the newsgroup, it seems like almost everyone that has moved to 2.2.1 through installation of the new All-In-One build is having this problem. Fortunately, there is an easy fix. The problem is related to a change in the Eclipse.ini file. This is a bug on the entire platform and affects all of the Eclipse products, not just BIRT. To fix open the Eclipse.ini file in your ECLIPSE_HOME directory. Find the line with
Replace that line with
That should solve the problem. The platform team is tracking this bug here. They are trying to make a decision
to release a new version of the platform or not. The BIRT team is also tracking the issue here.
Depending on what the platform team does with a new release, we may create a new 2.2.1a build of BIRT so that
this problem does not continue to exist.
Updated: It has come to my attention that there could be a couple of issues.
First) -XX:MaxPermSize=256m has to be the last line in the eclipse.ini
Second) There is only a single dash before the XX:MaxPermSize
Here is the complete eclipse.ini that I am using on my system. I have bumped the memory numbers a bit since I have plenty of RAM on my system.