[WICKET-5570] Rescheduling the same ajax timer behavior causes memory leak in the browser

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 6.14.0
• Fix Version/s: 7.0.0-M1, 6.16.0
• Component/s: wicket
• Assignee: Martin Tzvetanov Grigorov
• Reporter: Martin Tzvetanov Grigorov
• Created: 23/Apr/14 13:06
• Updated: 24/Jan/18 09:20
• Resolved: 23/Apr/14 13:21

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.

Issue Links

• is related to: WICKET-6523 Two AbstractAjaxTimerBehaviors on same component timeId conflict
• links to: The report of the bug in the mailing lists