Home » Eclipse Projects » Remote Application Platform (RAP) » Browser memory leak?
| Browser memory leak? [message #79238] |
Wed, 26 March 2008 05:34  |
Eclipse User |
|
|
|
Hi,
In my application I have a welcome screen that refreshes itself every
few minutes. Problem is that every time this occurs the browser memory
grows (around 15mb in IE7 and around 1mb in Firefox 2 - IE7 crashes at
1.5Gb occupied memory :) ). For the refresh I'm disposing the old
objects and creating new ones.
As anyone experienced something like this? How can I dispose the JS part?
Thanks
Tiago
|
|
| |
| Re: Browser memory leak? [message #79356 is a reply to message #79283] |
Wed, 26 March 2008 13:45  |
| Eclipse User |
|
|
|
Hi Frank,
I'm not refreshing the whole page, just a few labels (with images, don't
know if it's important), using the UICallBack mechanism.
Thanks
Tiago
Frank Appel wrote:
> Hi,
>
> does the welcome screen already exists as a RAP application? If so, I
> don't think it's a good idea anyway to refresh the whole page, since
> this triggers a complete session restart in RAP. I don't know where you
> get the memory leak, but couldn't you come to an equal solution using
> the UICallBack mechanism of RAP?
>
>
> Ciao
> Frank
>
> -----Ursprüngliche Nachricht-----
> Von: Tiago [mailto:tiago.bugzilla@gmail.com]
> Bereitgestellt: Mittwoch, 26. März 2008 10:34
> Bereitgestellt in: eclipse.technology.rap
> Unterhaltung: Browser memory leak?
> Betreff: Browser memory leak?
>
>
> Hi,
>
> In my application I have a welcome screen that refreshes itself every
> few minutes. Problem is that every time this occurs the browser memory
> grows (around 15mb in IE7 and around 1mb in Firefox 2 - IE7 crashes at
> 1.5Gb occupied memory :) ). For the refresh I'm disposing the old
> objects and creating new ones.
>
> As anyone experienced something like this? How can I dispose the JS
> part?
>
> Thanks
>
> Tiago
>
|
|
|
| Re: Browser memory leak? [message #79446 is a reply to message #79356] |
Thu, 27 March 2008 06:04 |
| Eclipse User |
|
|
|
Originally posted by: fappel.innoopract.com
Hi,
From our current point of view, we cannot explain the reason for this.
Could you please provide us a little snippet to reproduce the problem
for investigation? Just in case - which RAP version do you use?
Ciao
Frank
-----Ursprüngliche Nachricht-----
Von: Tiago [mailto:tiago.bugzilla@gmail.com]
Bereitgestellt: Mittwoch, 26. März 2008 18:45
Bereitgestellt in: eclipse.technology.rap
Unterhaltung: Browser memory leak?
Betreff: Re: Browser memory leak?
Hi Frank,
I'm not refreshing the whole page, just a few labels (with images, don't
know if it's important), using the UICallBack mechanism.
Thanks
Tiago
Frank Appel wrote:
> Hi,
>
> does the welcome screen already exists as a RAP application? If so, I
> don't think it's a good idea anyway to refresh the whole page, since
> this triggers a complete session restart in RAP. I don't know where
> you get the memory leak, but couldn't you come to an equal solution
> using the UICallBack mechanism of RAP?
>
>
> Ciao
> Frank
>
> -----Ursprüngliche Nachricht-----
> Von: Tiago [mailto:tiago.bugzilla@gmail.com]
> Bereitgestellt: Mittwoch, 26. März 2008 10:34 Bereitgestellt in:
> eclipse.technology.rap
> Unterhaltung: Browser memory leak?
> Betreff: Browser memory leak?
>
>
> Hi,
>
> In my application I have a welcome screen that refreshes itself every
> few minutes. Problem is that every time this occurs the browser memory
> grows (around 15mb in IE7 and around 1mb in Firefox 2 - IE7 crashes at
> 1.5Gb occupied memory :) ). For the refresh I'm disposing the old
> objects and creating new ones.
>
> As anyone experienced something like this? How can I dispose the JS
> part?
>
> Thanks
>
> Tiago
>
|
|
| |
| Re: Browser memory leak? [message #79699 is a reply to message #79459] |
Fri, 28 March 2008 05:59 |
| Eclipse User |
|
|
|
Originally posted by: fappel.innoopract.com
Hi,
thanks for the snippet, I will have a look at it asap.
Ciao
Frank
-----Ursprüngliche Nachricht-----
Von: Tiago [mailto:tiago.bugzilla@gmail.com]
Bereitgestellt: Donnerstag, 27. März 2008 13:12
Bereitgestellt in: eclipse.technology.rap
Unterhaltung: Browser memory leak?
Betreff: Re: Browser memory leak?
Hi Frank,
Please find the attached composite that replicates the problem. At the
end of the 50 refreshes defined in the top, my IE7 reports 205 Mb of
occupied memory (started with 45 Mb).
I'm currently using the CVS head from 05/03/2008 as M2 had a blocking
bug for me.
Tiago
Frank Appel wrote:
> Hi,
>
> From our current point of view, we cannot explain the reason for this.
> Could you please provide us a little snippet to reproduce the problem
> for investigation? Just in case - which RAP version do you use?
>
>
> Ciao
> Frank
>
>
> -----Ursprüngliche Nachricht-----
> Von: Tiago [mailto:tiago.bugzilla@gmail.com]
> Bereitgestellt: Mittwoch, 26. März 2008 18:45 Bereitgestellt in:
> eclipse.technology.rap
> Unterhaltung: Browser memory leak?
> Betreff: Re: Browser memory leak?
>
>
> Hi Frank,
>
> I'm not refreshing the whole page, just a few labels (with images,
> don't know if it's important), using the UICallBack mechanism.
>
> Thanks
>
> Tiago
>
> Frank Appel wrote:
>> Hi,
>>
>> does the welcome screen already exists as a RAP application? If so, I
>> don't think it's a good idea anyway to refresh the whole page, since
>> this triggers a complete session restart in RAP. I don't know where
>> you get the memory leak, but couldn't you come to an equal solution
>> using the UICallBack mechanism of RAP?
>>
>>
>> Ciao
>> Frank
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Tiago [mailto:tiago.bugzilla@gmail.com]
>> Bereitgestellt: Mittwoch, 26. März 2008 10:34 Bereitgestellt in:
>> eclipse.technology.rap
>> Unterhaltung: Browser memory leak?
>> Betreff: Browser memory leak?
>>
>>
>> Hi,
>>
>> In my application I have a welcome screen that refreshes itself every
>> few minutes. Problem is that every time this occurs the browser
>> memory
>
>> grows (around 15mb in IE7 and around 1mb in Firefox 2 - IE7 crashes
>> at
>
>> 1.5Gb occupied memory :) ). For the refresh I'm disposing the old
>> objects and creating new ones.
>>
>> As anyone experienced something like this? How can I dispose the JS
>> part?
>>
>> Thanks
>>
>> Tiago
>>
>
|
|
|
| Re: Browser memory leak? [message #80618 is a reply to message #79459] |
Tue, 01 April 2008 08:01 |
| Eclipse User |
|
|
|
Originally posted by: fappel.innoopract.com
Hi,
I could reproduce the problem using your snippet. I think your problem
belongs also to the bugs #204107, #203499, #202230, #199142, which are
targeting the client side widget pooling problem. Garbage Collection of
Browsers is not that what we are used to in JVMs. So ist
Ciao
Frank
-----Ursprüngliche Nachricht-----
Von: Tiago [mailto:tiago.bugzilla@gmail.com]
Bereitgestellt: Donnerstag, 27. März 2008 13:12
Bereitgestellt in: eclipse.technology.rap
Unterhaltung: Browser memory leak?
Betreff: Re: Browser memory leak?
Hi Frank,
Please find the attached composite that replicates the problem. At the
end of the 50 refreshes defined in the top, my IE7 reports 205 Mb of
occupied memory (started with 45 Mb).
I'm currently using the CVS head from 05/03/2008 as M2 had a blocking
bug for me.
Tiago
Frank Appel wrote:
> Hi,
>
> From our current point of view, we cannot explain the reason for this.
> Could you please provide us a little snippet to reproduce the problem
> for investigation? Just in case - which RAP version do you use?
>
>
> Ciao
> Frank
>
>
> -----Ursprüngliche Nachricht-----
> Von: Tiago [mailto:tiago.bugzilla@gmail.com]
> Bereitgestellt: Mittwoch, 26. März 2008 18:45 Bereitgestellt in:
> eclipse.technology.rap
> Unterhaltung: Browser memory leak?
> Betreff: Re: Browser memory leak?
>
>
> Hi Frank,
>
> I'm not refreshing the whole page, just a few labels (with images,
> don't know if it's important), using the UICallBack mechanism.
>
> Thanks
>
> Tiago
>
> Frank Appel wrote:
>> Hi,
>>
>> does the welcome screen already exists as a RAP application? If so, I
>> don't think it's a good idea anyway to refresh the whole page, since
>> this triggers a complete session restart in RAP. I don't know where
>> you get the memory leak, but couldn't you come to an equal solution
>> using the UICallBack mechanism of RAP?
>>
>>
>> Ciao
>> Frank
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Tiago [mailto:tiago.bugzilla@gmail.com]
>> Bereitgestellt: Mittwoch, 26. März 2008 10:34 Bereitgestellt in:
>> eclipse.technology.rap
>> Unterhaltung: Browser memory leak?
>> Betreff: Browser memory leak?
>>
>>
>> Hi,
>>
>> In my application I have a welcome screen that refreshes itself every
>> few minutes. Problem is that every time this occurs the browser
>> memory
>
>> grows (around 15mb in IE7 and around 1mb in Firefox 2 - IE7 crashes
>> at
>
>> 1.5Gb occupied memory :) ). For the refresh I'm disposing the old
>> objects and creating new ones.
>>
>> As anyone experienced something like this? How can I dispose the JS
>> part?
>>
>> Thanks
>>
>> Tiago
>>
>
|
|
|
| Re: Browser memory leak? [message #80632 is a reply to message #79459] |
Tue, 01 April 2008 08:17 |
| Eclipse User |
|
|
|
Originally posted by: fappel.innoopract.com
Hi,
I could reproduce the problem using your snippet. I think your problem
belongs also to the bugs #204107, #203499, #202230, #199142, which are
targeting the client side widget pooling problem.
Garbage Collection of Browsers is not that what we are used to in JVMs.
So its far more unpredictable if and when it happens. So in fact there
is a increase of memory consumption on the client the longer the
application is alive. To solve the problem we decided to introduce a
client side widget pooling mechanism. Unfortunately due to bugs in
Qooxdoo which could not be resolved in Qooxdoo 0.7.x, we had to
deactivate that mechanism again. But we have been reassured that these
problems will be solved with 0.8.x. As we already started the Qooxdoo
0.8.x integration work, there will be a solution to this asap.
By the way, did you check the behavior with IE 8 Beta or FireFox 3 Beta?
Ciao
Frank
-----Ursprüngliche Nachricht-----
Von: Tiago [mailto:tiago.bugzilla@gmail.com]
Bereitgestellt: Donnerstag, 27. März 2008 13:12
Bereitgestellt in: eclipse.technology.rap
Unterhaltung: Browser memory leak?
Betreff: Re: Browser memory leak?
Hi Frank,
Please find the attached composite that replicates the problem. At the
end of the 50 refreshes defined in the top, my IE7 reports 205 Mb of
occupied memory (started with 45 Mb).
I'm currently using the CVS head from 05/03/2008 as M2 had a blocking
bug for me.
Tiago
Frank Appel wrote:
> Hi,
>
> From our current point of view, we cannot explain the reason for this.
> Could you please provide us a little snippet to reproduce the problem
> for investigation? Just in case - which RAP version do you use?
>
>
> Ciao
> Frank
>
>
> -----Ursprüngliche Nachricht-----
> Von: Tiago [mailto:tiago.bugzilla@gmail.com]
> Bereitgestellt: Mittwoch, 26. März 2008 18:45 Bereitgestellt in:
> eclipse.technology.rap
> Unterhaltung: Browser memory leak?
> Betreff: Re: Browser memory leak?
>
>
> Hi Frank,
>
> I'm not refreshing the whole page, just a few labels (with images,
> don't know if it's important), using the UICallBack mechanism.
>
> Thanks
>
> Tiago
>
> Frank Appel wrote:
>> Hi,
>>
>> does the welcome screen already exists as a RAP application? If so, I
>> don't think it's a good idea anyway to refresh the whole page, since
>> this triggers a complete session restart in RAP. I don't know where
>> you get the memory leak, but couldn't you come to an equal solution
>> using the UICallBack mechanism of RAP?
>>
>>
>> Ciao
>> Frank
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Tiago [mailto:tiago.bugzilla@gmail.com]
>> Bereitgestellt: Mittwoch, 26. März 2008 10:34 Bereitgestellt in:
>> eclipse.technology.rap
>> Unterhaltung: Browser memory leak?
>> Betreff: Browser memory leak?
>>
>>
>> Hi,
>>
>> In my application I have a welcome screen that refreshes itself every
>> few minutes. Problem is that every time this occurs the browser
>> memory
>
>> grows (around 15mb in IE7 and around 1mb in Firefox 2 - IE7 crashes
>> at
>
>> 1.5Gb occupied memory :) ). For the refresh I'm disposing the old
>> objects and creating new ones.
>>
>> As anyone experienced something like this? How can I dispose the JS
>> part?
>>
>> Thanks
>>
>> Tiago
>>
>
|
|
|
| Re: Browser memory leak? [message #80647 is a reply to message #80632] |
Tue, 01 April 2008 08:21 |
| Eclipse User |
|
|
|
Originally posted by: fappel.innoopract.com
Hi,
just another thought: in your example you dispose of all items each time
a refresh takes place. I don't know if this could work in your
application, but reusing the items instead of disposing them would
improve the situation of course.
Ciao
Frank
-----Ursprüngliche Nachricht-----
Von: Frank Appel [mailto:fappel@innoopract.com]
Bereitgestellt: Dienstag, 1. April 2008 14:18
Bereitgestellt in: eclipse.technology.rap
Unterhaltung: Browser memory leak?
Betreff: Re: Browser memory leak?
Hi,
I could reproduce the problem using your snippet. I think your problem
belongs also to the bugs #204107, #203499, #202230, #199142, which are
targeting the client side widget pooling problem.
Garbage Collection of Browsers is not that what we are used to in JVMs.
So its far more unpredictable if and when it happens. So in fact there
is a increase of memory consumption on the client the longer the
application is alive. To solve the problem we decided to introduce a
client side widget pooling mechanism. Unfortunately due to bugs in
Qooxdoo which could not be resolved in Qooxdoo 0.7.x, we had to
deactivate that mechanism again. But we have been reassured that these
problems will be solved with 0.8.x. As we already started the Qooxdoo
0.8.x integration work, there will be a solution to this asap.
By the way, did you check the behavior with IE 8 Beta or FireFox 3 Beta?
Ciao
Frank
-----Ursprüngliche Nachricht-----
Von: Tiago [mailto:tiago.bugzilla@gmail.com]
Bereitgestellt: Donnerstag, 27. März 2008 13:12 Bereitgestellt in:
eclipse.technology.rap
Unterhaltung: Browser memory leak?
Betreff: Re: Browser memory leak?
Hi Frank,
Please find the attached composite that replicates the problem. At the
end of the 50 refreshes defined in the top, my IE7 reports 205 Mb of
occupied memory (started with 45 Mb).
I'm currently using the CVS head from 05/03/2008 as M2 had a blocking
bug for me.
Tiago
Frank Appel wrote:
> Hi,
>
> From our current point of view, we cannot explain the reason for this.
> Could you please provide us a little snippet to reproduce the problem
> for investigation? Just in case - which RAP version do you use?
>
>
> Ciao
> Frank
>
>
> -----Ursprüngliche Nachricht-----
> Von: Tiago [mailto:tiago.bugzilla@gmail.com]
> Bereitgestellt: Mittwoch, 26. März 2008 18:45 Bereitgestellt in:
> eclipse.technology.rap
> Unterhaltung: Browser memory leak?
> Betreff: Re: Browser memory leak?
>
>
> Hi Frank,
>
> I'm not refreshing the whole page, just a few labels (with images,
> don't know if it's important), using the UICallBack mechanism.
>
> Thanks
>
> Tiago
>
> Frank Appel wrote:
>> Hi,
>>
>> does the welcome screen already exists as a RAP application? If so, I
>> don't think it's a good idea anyway to refresh the whole page, since
>> this triggers a complete session restart in RAP. I don't know where
>> you get the memory leak, but couldn't you come to an equal solution
>> using the UICallBack mechanism of RAP?
>>
>>
>> Ciao
>> Frank
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Tiago [mailto:tiago.bugzilla@gmail.com]
>> Bereitgestellt: Mittwoch, 26. März 2008 10:34 Bereitgestellt in:
>> eclipse.technology.rap
>> Unterhaltung: Browser memory leak?
>> Betreff: Browser memory leak?
>>
>>
>> Hi,
>>
>> In my application I have a welcome screen that refreshes itself every
>> few minutes. Problem is that every time this occurs the browser
>> memory
>
>> grows (around 15mb in IE7 and around 1mb in Firefox 2 - IE7 crashes
>> at
>
>> 1.5Gb occupied memory :) ). For the refresh I'm disposing the old
>> objects and creating new ones.
>>
>> As anyone experienced something like this? How can I dispose the JS
>> part?
>>
>> Thanks
>>
>> Tiago
>>
>
|
|
|
| Re: Browser memory leak? [message #80731 is a reply to message #80632] |
Tue, 01 April 2008 12:00 |
| Eclipse User |
|
|
|
Hi,
First of all thanks for you clarifications. Never tested it in IE8 Beta,
but in Firefox 3 Beta the behavior is similar to that of Firefox 2.
Tiago
Frank Appel wrote:
> Hi,
>
> I could reproduce the problem using your snippet. I think your problem
> belongs also to the bugs #204107, #203499, #202230, #199142, which are
> targeting the client side widget pooling problem.
>
> Garbage Collection of Browsers is not that what we are used to in JVMs.
> So its far more unpredictable if and when it happens. So in fact there
> is a increase of memory consumption on the client the longer the
> application is alive. To solve the problem we decided to introduce a
> client side widget pooling mechanism. Unfortunately due to bugs in
> Qooxdoo which could not be resolved in Qooxdoo 0.7.x, we had to
> deactivate that mechanism again. But we have been reassured that these
> problems will be solved with 0.8.x. As we already started the Qooxdoo
> 0.8.x integration work, there will be a solution to this asap.
>
> By the way, did you check the behavior with IE 8 Beta or FireFox 3 Beta?
>
> Ciao
> Frank
>
> -----Ursprüngliche Nachricht-----
> Von: Tiago [mailto:tiago.bugzilla@gmail.com]
> Bereitgestellt: Donnerstag, 27. März 2008 13:12
> Bereitgestellt in: eclipse.technology.rap
> Unterhaltung: Browser memory leak?
> Betreff: Re: Browser memory leak?
>
>
> Hi Frank,
>
> Please find the attached composite that replicates the problem. At the
> end of the 50 refreshes defined in the top, my IE7 reports 205 Mb of
> occupied memory (started with 45 Mb).
>
> I'm currently using the CVS head from 05/03/2008 as M2 had a blocking
> bug for me.
>
> Tiago
>
> Frank Appel wrote:
>> Hi,
>>
>> From our current point of view, we cannot explain the reason for this.
>> Could you please provide us a little snippet to reproduce the problem
>> for investigation? Just in case - which RAP version do you use?
>>
>>
>> Ciao
>> Frank
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Tiago [mailto:tiago.bugzilla@gmail.com]
>> Bereitgestellt: Mittwoch, 26. März 2008 18:45 Bereitgestellt in:
>> eclipse.technology.rap
>> Unterhaltung: Browser memory leak?
>> Betreff: Re: Browser memory leak?
>>
>>
>> Hi Frank,
>>
>> I'm not refreshing the whole page, just a few labels (with images,
>> don't know if it's important), using the UICallBack mechanism.
>>
>> Thanks
>>
>> Tiago
>>
>> Frank Appel wrote:
>>> Hi,
>>>
>>> does the welcome screen already exists as a RAP application? If so, I
>
>>> don't think it's a good idea anyway to refresh the whole page, since
>>> this triggers a complete session restart in RAP. I don't know where
>>> you get the memory leak, but couldn't you come to an equal solution
>>> using the UICallBack mechanism of RAP?
>>>
>>>
>>> Ciao
>>> Frank
>>>
>>> -----Ursprüngliche Nachricht-----
>>> Von: Tiago [mailto:tiago.bugzilla@gmail.com]
>>> Bereitgestellt: Mittwoch, 26. März 2008 10:34 Bereitgestellt in:
>>> eclipse.technology.rap
>>> Unterhaltung: Browser memory leak?
>>> Betreff: Browser memory leak?
>>>
>>>
>>> Hi,
>>>
>>> In my application I have a welcome screen that refreshes itself every
>
>>> few minutes. Problem is that every time this occurs the browser
>>> memory
>>> grows (around 15mb in IE7 and around 1mb in Firefox 2 - IE7 crashes
>>> at
>>> 1.5Gb occupied memory :) ). For the refresh I'm disposing the old
>>> objects and creating new ones.
>>>
>>> As anyone experienced something like this? How can I dispose the JS
>>> part?
>>>
>>> Thanks
>>>
>>> Tiago
>>>
>
>
|
|
|
| Re: Browser memory leak? [message #80737 is a reply to message #80647] |
Tue, 01 April 2008 12:09 |
| Eclipse User |
|
|
|
Hi,
I've already considered your suggested approach and we're going to try
and implement it to see if it improves.
Thanks again.
Tiago
Frank Appel wrote:
> Hi,
>
> just another thought: in your example you dispose of all items each time
> a refresh takes place. I don't know if this could work in your
> application, but reusing the items instead of disposing them would
> improve the situation of course.
>
>
> Ciao
> Frank
>
> -----Ursprüngliche Nachricht-----
> Von: Frank Appel [mailto:fappel@innoopract.com]
> Bereitgestellt: Dienstag, 1. April 2008 14:18
> Bereitgestellt in: eclipse.technology.rap
> Unterhaltung: Browser memory leak?
> Betreff: Re: Browser memory leak?
>
>
> Hi,
>
> I could reproduce the problem using your snippet. I think your problem
> belongs also to the bugs #204107, #203499, #202230, #199142, which are
> targeting the client side widget pooling problem.
>
> Garbage Collection of Browsers is not that what we are used to in JVMs.
> So its far more unpredictable if and when it happens. So in fact there
> is a increase of memory consumption on the client the longer the
> application is alive. To solve the problem we decided to introduce a
> client side widget pooling mechanism. Unfortunately due to bugs in
> Qooxdoo which could not be resolved in Qooxdoo 0.7.x, we had to
> deactivate that mechanism again. But we have been reassured that these
> problems will be solved with 0.8.x. As we already started the Qooxdoo
> 0.8.x integration work, there will be a solution to this asap.
>
> By the way, did you check the behavior with IE 8 Beta or FireFox 3 Beta?
>
> Ciao
> Frank
>
> -----Ursprüngliche Nachricht-----
> Von: Tiago [mailto:tiago.bugzilla@gmail.com]
> Bereitgestellt: Donnerstag, 27. März 2008 13:12 Bereitgestellt in:
> eclipse.technology.rap
> Unterhaltung: Browser memory leak?
> Betreff: Re: Browser memory leak?
>
>
> Hi Frank,
>
> Please find the attached composite that replicates the problem. At the
> end of the 50 refreshes defined in the top, my IE7 reports 205 Mb of
> occupied memory (started with 45 Mb).
>
> I'm currently using the CVS head from 05/03/2008 as M2 had a blocking
> bug for me.
>
> Tiago
>
> Frank Appel wrote:
>> Hi,
>>
>> From our current point of view, we cannot explain the reason for this.
>> Could you please provide us a little snippet to reproduce the problem
>> for investigation? Just in case - which RAP version do you use?
>>
>>
>> Ciao
>> Frank
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Tiago [mailto:tiago.bugzilla@gmail.com]
>> Bereitgestellt: Mittwoch, 26. März 2008 18:45 Bereitgestellt in:
>> eclipse.technology.rap
>> Unterhaltung: Browser memory leak?
>> Betreff: Re: Browser memory leak?
>>
>>
>> Hi Frank,
>>
>> I'm not refreshing the whole page, just a few labels (with images,
>> don't know if it's important), using the UICallBack mechanism.
>>
>> Thanks
>>
>> Tiago
>>
>> Frank Appel wrote:
>>> Hi,
>>>
>>> does the welcome screen already exists as a RAP application? If so, I
>
>>> don't think it's a good idea anyway to refresh the whole page, since
>>> this triggers a complete session restart in RAP. I don't know where
>>> you get the memory leak, but couldn't you come to an equal solution
>>> using the UICallBack mechanism of RAP?
>>>
>>>
>>> Ciao
>>> Frank
>>>
>>> -----Ursprüngliche Nachricht-----
>>> Von: Tiago [mailto:tiago.bugzilla@gmail.com]
>>> Bereitgestellt: Mittwoch, 26. März 2008 10:34 Bereitgestellt in:
>>> eclipse.technology.rap
>>> Unterhaltung: Browser memory leak?
>>> Betreff: Browser memory leak?
>>>
>>>
>>> Hi,
>>>
>>> In my application I have a welcome screen that refreshes itself every
>
>>> few minutes. Problem is that every time this occurs the browser
>>> memory
>>> grows (around 15mb in IE7 and around 1mb in Firefox 2 - IE7 crashes
>>> at
>>> 1.5Gb occupied memory :) ). For the refresh I'm disposing the old
>>> objects and creating new ones.
>>>
>>> As anyone experienced something like this? How can I dispose the JS
>>> part?
>>>
>>> Thanks
>>>
>>> Tiago
>>>
>
>
|
|
|
Goto Forum:
Current Time: Sun May 11 19:56:40 EDT 2025
Powered by FUDForum. Page generated in 0.03673 seconds |
Home