ICEfaces
  1. ICEfaces
  2. ICE-5628

Memory leak in IE7 using icefaces2

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 2.0-Alpha3
          • Fix Version/s: 2.0-Alpha3, 2.0.0
          • Component/s: Bridge
          • Labels:
            None
          • Environment:
            IE7 & Glassfishv3-final

            Description

            Auction application was left running over night on glassfiahv3 final server. Below are the memory readings:

            Day1 morning 20,528
                      Day1 evening 335,260
                      Day2 morning 536,756
                      Minimize 502,192
                      Maximize 523,912


            Memory readings for auctionMonitor are as follows:

                       Day1 morning 45,316
                       Day1 evening 986,012
                             

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Mircea Toma added a comment - - edited

              It seems that when the form used by retrieveUpdates() and singleSubmit() is cloned, even if not appended to the document, generates memory leaks in IE.
              The solution was to use the form directly by just editing its attributes or append elements, after the request is made the edited values are rolled back and appended elements removed.

              Show
              Mircea Toma added a comment - - edited It seems that when the form used by retrieveUpdates() and singleSubmit() is cloned, even if not appended to the document, generates memory leaks in IE. The solution was to use the form directly by just editing its attributes or append elements, after the request is made the edited values are rolled back and appended elements removed.
              Hide
              Permalink
              Ken Fyten added a comment -

              QA reports that the leak still occurs with IE:

              Mandeep says:

              Looks like the memory leak is still present

              Revision# 21290
              auctionMonitor icepc13

              Start End
              IE7 46,156 972,244 (clocks stop ticking)

              Auction tests are starting now, so should have results by end of today.

              Show
              Ken Fyten added a comment - QA reports that the leak still occurs with IE: Mandeep says: Looks like the memory leak is still present Revision# 21290 auctionMonitor icepc13 Start End IE7 46,156 972,244 (clocks stop ticking) Auction tests are starting now, so should have results by end of today.
              Hide
              Permalink
              Ken Fyten added a comment -

              Reran browser memory test:
              auction ICEPC18

              IE7 31,708 403,236 (clocks stopped ticking)

              auctionMonitor ICEPC13
              IE7 44,064 969,804 (clocks stopped ticking)

              The browser cache was clean.

              Regards,
              Mandeep

              Show
              Ken Fyten added a comment - Reran browser memory test: auction ICEPC18 IE7 31,708 403,236 (clocks stopped ticking) auctionMonitor ICEPC13 IE7 44,064 969,804 (clocks stopped ticking) The browser cache was clean. Regards, Mandeep
              Hide
              Permalink
              Mircea Toma added a comment - - edited

              The Mojarra 2.0.2 libraries don't contain the fix we sent for the memory leak in JSF bridge: https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=1521 . The tests should be run with libraries build from code with the revision greater than #8306 (Mojarra repository).

              Show
              Mircea Toma added a comment - - edited The Mojarra 2.0.2 libraries don't contain the fix we sent for the memory leak in JSF bridge: https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=1521 . The tests should be run with libraries build from code with the revision greater than #8306 (Mojarra repository).
              Hide
              Permalink
              Ken Fyten added a comment -

              Weekend testing confirms that this leak is fixed. Tested versions are:

              Glimmer revision: 21420
              jsf2.0-mojarra-r8306
              Server: Tomcat 6.0.26

              Show
              Ken Fyten added a comment - Weekend testing confirms that this leak is fixed. Tested versions are: Glimmer revision: 21420 jsf2.0-mojarra-r8306 Server: Tomcat 6.0.26

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  Mandeep Hayher
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: