This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | memory leak in JspParserImpl | ||
---|---|---|---|
Product: | javaee | Reporter: | Quy Nguyen <quynguyen> |
Component: | JSP Parser | Assignee: | Tomas Mysik <tmysik> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | CC: | pjiricka, ppisl |
Priority: | P2 | Keywords: | PERFORMANCE |
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 123530 |
Description
Quy Nguyen
2008-01-11 01:42:26 UTC
Hi Quy, how big is the leak and when does it happen? Without this we can not say how serious this bug is a what should be the priority. Assigning to Tomas as he will be looking at the JSP parser performance/memory problems. It at least happens every time a visual web project (or a page within that project) is opened. I am not sure if it occurs as regularly with plain web projects. As for the severity of the leak, see: http://wiki.netbeans.org/wiki/view/DevFaqMemoryLeaks It specifically mentions Project instances as serious memory leaks. In this case, every WebProject object is retained in memory (so opening 5 web projects retains all 5 corresponding WebProject objects). Therefore, I think P2 is the correct priority with this issue. JSPParser should be rewritten in NB 6.1. *** This issue has been marked as a duplicate of 85817 *** |