Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 1.2 final
-
Fix Version/s: 1.2.1
-
Component/s: View technologies
-
Labels:None
-
Environment:Sun JDK 6, tomcat 6, bug caught with netbeans profile, hprof, mat...groovy grails project
Description
When our application renders huge data(per say 8MB) using sitemesh (which is a default filter in grails, looks like, not sure) leads to double the datasize memory leak(16MB)..this was found during stress testing of our web application.
Issue Links
| This issue is related to: | ||||
| GRAILS-5733 | Netbeans profiler shows in the heapdump Inspect option that - "org.codehaus.groovy.grails.web.util.StreamCharBuffer" as the biggest object retained |
|
|
|
This is normal since sitemesh will render the page (which is probably 8mb) then render the layout WITH the page embedded (another 8mb). To be honest 8m is a HUGE amount of date and sitemesh doesn't seem to be an appropriate solution in your use case and I would look to remove the sitemesh layer