Side navigation
#10889 closed bug (invalid)
Opened November 25, 2011 12:14AM UTC
Closed December 13, 2011 07:59AM UTC
Last modified March 14, 2012 11:30AM UTC
Memory utilized by the browser keeps rising - sizcache is incrementing with every refresh
| Reported by: | sumant.panda@techmahindra.com | Owned by: | sumant.panda@techmahindra.com |
|---|---|---|---|
| Priority: | undecided | Milestone: | None |
| Component: | unfiled | Version: | 1.3.2 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
We are using Primefaces provided JSF components in the application.
There are a few scenarios in which we do some datatable refresh, but on every refresh the memory utilized by the browser keeps rising.
There’s an attribute sizcache and it keeps increasing on each refresh, it’s associated with tbody, td, tr, div etc…
<DIV id=sidebar1 class="ui-widget-content ui-corner-all ui-helper-clearfix sidebar" sizcache="9118" sizset="0">
<UL sizcache="9118" sizset="0">
<LI sizcache="9118" sizset="0">
<TABLE sizcache="9118" sizset="0">
<TBODY sizcache="9118" sizset="0">
<TR>
<TD style="PADDING-BOTTOM: 8px; PADDING-LEFT: 8px; PADDING-RIGHT: 8px; PADDING-TOP: 8px" colSpan=2 align=left>
Having googled a loty around the issue, I've zeroed in on a probable bug in JQuery that I need to resolve with real urgency.Please help in identifying the reason for the issue and resolving it .
You could replicate the same issue on the primefaces showcase - http://www.primefaces.org/showcase/ui/datatableComplex.jsf
How to replicate - Navigate between page 1 to 5 multiple times, try doing some sorting on a few of the columns, monitor the memory utilized, you can see it constantly rising…
Thanks and Regards
Sumant
Attachments (0)
Change History (3)
Changed November 28, 2011 09:02PM UTC by comment:1
Changed November 28, 2011 09:13PM UTC by comment:2
| owner: | → sumant.panda@techmahindra.com |
|---|---|
| status: | new → pending |
Changed December 13, 2011 07:59AM UTC by comment:3
| resolution: | → invalid |
|---|---|
| status: | pending → closed |
Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!
Thanks for taking the time to contribute to the jQuery project! Please provide a complete reduced test case on jsFiddle to help us assess your ticket.
Additionally, be sure to test against the jQuery Edge version to ensure the issue still exists. To get you started, use this boilerplate: http://jsfiddle.net/FrKyN/ Open the link and click to "Fork" (in the top menu) to get started.