Uploaded image for project: 'Wicket'
  1. Wicket
  2. WICKET-5570

Rescheduling the same ajax timer behavior causes memory leak in the browser

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 6.14.0
    • 7.0.0-M1, 6.16.0
    • wicket
    • None

    Description

      AbstractAjaxTimerBehavior uses JavaScript setTimeout() function to do its job. It has a #stop() method that clears the timeout but if the timeout is re-scheduled without being cleared a memory leak is observed in the browser.

      Attachments

        1. wicket-push-test.zip
          38 kB
          Martin Tzvetanov Grigorov

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. WICKET-6523 Two AbstractAjaxTimerBehaviors on same component timeId conflict

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          links to

          Web Link The report of the bug in the mailing lists

          Activity

            People

              mgrigorov Martin Tzvetanov Grigorov
              mgrigorov Martin Tzvetanov Grigorov
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: