[TAPESTRY-178] possible memory leak when disable-caching is true

• Type: Bug
• Status: Resolved
• Resolution: Won't Fix
• Affects Version/s: 3.0
• Component/s: Framework
• Environment: Operating System: Windows XP; Platform: PC
• Bugzilla Id: 29253
• Assignee: Unassigned
• Reporter: Galen Meurer
• Created: 28/May/04 01:38
• Updated: 07/Mar/06 10:57
• Resolved: 07/Mar/06 10:57

Description

JBoss 3.2.3, XP SP2

We expect Out Of Memory errors when hot deploying, but this is not that. With
disable-caching set to true, you can reload the same page over and over and
watch the memory consumption increase. With disable-caching to false,
reloading the same page will cause memory consumption to raise slightly in the
first few loads, but level off and remain constant.

The severity of the leak seems to be related to the number of components on
the page.

We have a page with a lot of components, some of them nested 3 deep. We have
seen this using both an exploded EAR and an EAR file.

You can reproduce this with the workbench example from release 3.0. Deploying
just that war and reloading just the Fields tab (not interacting with it, just
reloading), I saw the following:

(Using Windows Task Manager – all #s in K)

(Mem Usage) (VM Size)
Startup: 45,788 47,824
Workbench Load: 45,852 51,280
Fields Load 1: 50,800 54,064
Fields Load 2: 51,468 58,240
Fields Load 3: 53,176 58,352
Fields Load 4: 54,936 58,332
Fields Load 5: 55,416 61,576
Fields Load 6: 56,696 62,600
Fields Load 7: 56,172 64,288
Fields Load 8: 58,112 65,152
Fields Load 9: 59,492 65,012
Fields Load 10: 61,632 65,388
...
Fields Load 20: 68,788 76,752
...
Fields Load 30: 76,384 83,238
...
Fields Load 40: 85,720 93,460
...
Fields Load 50: 95,808 101,240
...
Fields Load 100: 106,780 107,916

Our large page displays the following behavior:

– Caching Disabled – [using windows task manager on XP]

(Mem Usage) (VM Size)
Startup: 64,424K 66,172K
Login/Dashboard Load: 76,752K 75,480K
Case Load 1: 78,632K 86,444K
Case Reload 2: 83,008K 87,788K
Case Reload 3: 87,948K 96,736K
Case Reload 4: 88,920K 97,812K
Case Reload 5: 91,424K 98,608K
Case Reload 6: 92,212K 103,556K
Case Reload 7: 94,540K 103,972K
...
Case Reload 20: 115,348K 118,536K

– Caching Enabled –

(Mem Usage) (VM Size)
Startup: 62,616K 64,712K
Login/Dashboard Load: 69,132K 75,688K
Case Load 1: 72,892K 76,344K
Case Reload 2: 73,368K 89,068K
Case Reload 3: 74,504K 89,396K
Case Reload 4: 74,556K 89,396K
Case Reload 5: 74,924K 89,748K
Case Reload 6: 74,708K 89,236K
Case Reload 7: 74,748K 89,280K
...
Case Reload 20: 76,160K 90,912K
...
Case Reload 35: 76,608K 91,240K