| BIRT Out Of Memory issues [message #652199] |
Wed, 02 February 2011 20:18  |
Eclipse User |
|
|
|
Hi guys,
Ive been having a lot of out of memory issues with BIRT reports over the last few months. All information regarding this online seems to suggest just increasing the heap size and tweaking various memory settings. At best these all just delay the issue.
However, I think I've stumbled upon a solution (or at least it was in my situation). Just posting up in case anyone else might be encountering the same thing.
In my case, the issue was to do with custom javascript which I had added. For some reason, any local variables declared were not being cleared from memory once the function had finished running.
So if you have a function:
function getSomething()
{
a = "hello";
b = "world";
return "something";
}
If you ran this function multiple times, it was using up new memory blocks for the a and b variables at each run.
The moment I modified my javascript functions to explicitly destroy the variables, all my out of memory issues were no longer occurring;
function getSomething()
{
a = "hello";
b = "world";
delete a;
delete b;
return "something";
}
Note: I am still getting memory issues. However, now the issue is that eclipse crashes with out of memory error *after* my report is generated. So at least I can actually see my report now.
|
|
|
| Re: BIRT Out Of Memory issues [message #652364 is a reply to message #652199] |
Thu, 03 February 2011 11:33  |
| Eclipse User |
|
|
|
Just curious is using var instead of the delete would work.
Jason
On 2/2/2011 8:18 PM, tkuchhal@gmail.com wrote:
> Hi guys,
>
> Ive been having a lot of out of memory issues with BIRT reports over the
> last few months. All information regarding this online seems to suggest
> just increasing the heap size and tweaking various memory settings. At
> best these all just delay the issue.
>
> However, I think I've stumbled upon a solution (or at least it was in my
> situation). Just posting up in case anyone else might be encountering
> the same thing.
> In my case, the issue was to do with custom javascript which I had
> added. For some reason, any local variables declared were not being
> cleared from memory once the function had finished running.
>
> So if you have a function:
>
> function getSomething()
> {
> a = "hello";
> b = "world";
>
> return "something";
> }
>
> If you ran this function multiple times, it was using up new memory
> blocks for the a and b variables at each run.
>
> The moment I modified my javascript functions to explicitly destroy the
> variables, all my out of memory issues were no longer occurring;
>
> function getSomething()
> {
> a = "hello";
> b = "world";
>
> delete a;
> delete b;
> return "something";
> }
>
>
> Note: I am still getting memory issues. However, now the issue is that
> eclipse crashes with out of memory error *after* my report is generated.
> So at least I can actually see my report now.
|
|
|
Powered by
FUDForum. Page generated in 0.03753 seconds
Home