This is what I typically do in such circumstances, may work in your case too. Pardon me if this appears to be "preaching the choir".
On Sunday, May 1, 2016 at 5:51:04 AM UTC-4, thamarai kannan wrote:
-- Step 1 - Detect which component leaks memory
I will disable the code behind each component, one by one. The last component disabled that stopped the memory leak may be the culprit.
Step 2 - Create a POE (Proof of Error)
This will be a whittled down component, hoping to retain the memory leak still, will be easy to diagnose by myself.
Step 3 - If step 2 fails share the code in a forum like this (I'm hoping it would be OK to share at this point) and ask for help.
This has worked for me so far. I hope it will help you too.
You may also want to try GWT 2.7, as Daniel Kurka has suggested.
On Sunday, May 1, 2016 at 5:51:04 AM UTC-4, thamarai kannan wrote:
Hi Velusamy sir,
sorry, I can not share the code. Is there any other way to find the root cause and fix.
On Friday, April 29, 2016 at 7:23:30 PM UTC+5:30, Velusamy Velu wrote:Thamarai Kannan:Any reason you chose GWT 2.5.1 instead of the latest version? As Gilberto responded it would be easier to pinpoint the problem if you could share your code, unless you are restricted.
On Monday, February 15, 2016 at 5:05:18 AM UTC-5, thamarai kannan wrote:Hi, I am using GWT Application. for this application I am using IE10. While lading another screen or reloading same page my RAM Memory increasing continously. Approximately each load 5MB RAM memory consuming. Anyone help me to free this memory space at the time of loading.
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment