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.

Bug 194448 - Evaluate possible memory leak
Summary: Evaluate possible memory leak
Status: RESOLVED FIXED
Alias: None
Product: web
Classification: Unclassified
Component: CSS Visual Tools (show other bugs)
Version: 7.0
Hardware: All All
: P2 normal (vote)
Assignee: Marek Fukala
URL:
Keywords:
Depends on:
Blocks: 191872
  Show dependency tree
 
Reported: 2011-01-18 19:59 UTC by Petr Jiricka
Modified: 2011-01-19 09:54 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Comment 1 Marek Fukala 2011-01-18 22:16:22 UTC
http://statistics.netbeans.org/exceptions/exception.do?id=431535 is a duplicate of already fixed issue 184423 - [69cat] OutOfMemoryError: Java heap space.


http://statistics.netbeans.org/exceptions/exception.do?id=430840

Shows three parser results held by parsing.api SourceCache. I remember there has been a bugfix by Tomas related to this last year. But I am not sure whether this may be the problem or not. Show in threads doesn't work for this heapdump for the java frame GC roots :-(
Comment 2 Marek Fukala 2011-01-18 22:22:49 UTC
There's the issue I mentioned: Bug 191497 - [70cat]IDE becomes slow when editing large HTML file
Comment 3 Marek Fukala 2011-01-19 09:00:08 UTC
OK, even the other heapdumps shows still the same problem as issue 194423 described. The issue has not been fixed in fact, the CharSequence returned from parsing.api Snapshot.getText() is a StringBuilder which does clone the text on subSequence(...).
Comment 4 Marek Fukala 2011-01-19 09:54:05 UTC
fixed in web-main#810b5292ece4

now most of the CssModel's Entry object properties are loaded lazily since most of them is never used (definitively not necessary during the indexing), and if a property of CharSequence type is requested it returns a wrapping CharSequence which doesn't clone the text but delegates to the source CHS.

Thanks for extracting these reports and creating the issue. I believe this fix will help a lot!