You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Igor Vaynberg (JIRA)" <ji...@apache.org> on 2010/11/14 08:22:13 UTC

[jira] Resolved: (WICKET-3160) Session causing memory leak after WICKET-3108

     [ https://issues.apache.org/jira/browse/WICKET-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Vaynberg resolved WICKET-3160.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.4.14
         Assignee: Igor Vaynberg

> Session causing memory leak after WICKET-3108
> ---------------------------------------------
>
>                 Key: WICKET-3160
>                 URL: https://issues.apache.org/jira/browse/WICKET-3160
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4.13
>            Reporter: Pedro Santos
>            Assignee: Igor Vaynberg
>             Fix For: 1.4.14
>
>         Attachments: fix-test-WICKET-3160-cleanup.patch, fix-test-WICKET-3160-maintainingLruSequence.patch, fix-test-WICKET-3160.patch, fix-WICKET-3108-memory-leak.patch
>
>
> Session has a not transient variable storing used pagemaps causing memory leak. Pagemap objects are already maintained by the session store object.
> Please see more info at https://issues.apache.org/jira/browse/WICKET-3108

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.