Re: Memory Leak and Trinidad Pagination

[Blake Sullivan]

This is because the current ChangeManager implementation doesn't collapse AttributeComponentChanges for a change to the same attribute on the same component. -- Blake Sullivan Azhaguramanhjam, Ramkumar said the following On 2/4/2009 7:39 AM PT: Hi This is regarding the usage of memory (Page Flow Scope) in Trinidad Pagination.I have a Custom Implementation by which each time it goes to database to fetch records but I see a problem as mentioned below Iam checking the memory leaks in session when I use the pagination. On each click of Next/Previous or Range Change  iam seeing an increase of 21 bytes of memory. I think for each action a token is put on a HashMap. This is never cleaned up until the session is invalidated(user logs off). Can this thing be cleaned up? On First Click of Next:(memory uage -537 bytes) org.apache.myfaces.trinidadinternal.Change (java.util.HashMap) 1 items: '{/jsf/zipPaginate.jspx={_id4:_id4=[org.apache.myfaces.trinidad.change. attributecomponentcha...@5dea5dea, org.apache.myfaces.trinidad.change. attributecomponentcha...@1e2e1e2e]}}' 537 After clicking Next twice iam seeing memory usage got increased by 42 bytes (now 579 bytes) org.apache.myfaces.trinidadinternal.Change (java.util.HashMap) 1 items: '{/jsf/zipPaginate.jspx={_id4:_id4=[org.apache.myfaces.trinidad.change. attributecomponentcha...@5dea5dea, org.apache.myfaces.trinidad.change. attributecomponentcha...@1e2e1e2e, org.apache.myfaces.trinidad.change. attributecomponentcha...@2b5c2b5c, org.apache.myfaces.trinidad.change. attributecomponentcha...@5f3a5f3a]}}' 579   Note: Here :_id4 represents the org.apache.myfaces.trinidad.component.core.data.CoreTable   Thanks Ramkumar A Phone:410-986-4672