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.
[nb_dev](20020923) If you unjar attached testCVS.jar and run IDETests, you will see that there is memory leak (~500kB per one run). Test provide actions described on the page http://qa.netbeans.org/man-suites/validation/ide/OverallValidation.html - part CVS test. Second attachment is graph of used memory (measured before/after test, before measure 5 times invoke GC, used=allocated-free).
Created attachment 7496 [details] testing classes
Created attachment 7497 [details] Graph of used memory
Changing TASK -> DEFECT. Please start to resolve performance issues, use some profiler tool on looking for leaks, for more inforamtion call performance team.
I can not do things concurrently ;( thus I will start solving this after I'll have basic projects integration done. Don't exepect this to be solved soon.
I am not pressing time,I know that you have more works on projects integration, but Perormance is the second target feature in next release, so I am changing Target milestone to 4.0.
The test case for possible memory leak should be re-ivestigated in the new projects integration.
Hi, this problem manifests in netbeans 5.5 and passed almost 5 years. Steps to reproduce are to fire cvs checkout on netbeans stable55 module on cvs.netbeans.org my system goes to more than 300M for the java process and performance is inacceptable, editing other project source file becomes very hard because of "please wait" on completions . Maybe a solution would be to fire the cvs on another process so that editing is still posible . My platform is windows.
We have new VCS impl and new memory leaks. This one is no longer important.
v/c