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.
Using the July 23 full install installer build, after opening the visualweb/dataconnectivity module (nothing else) I've been waiting for over 5 minutes just for scanning to complete. My laptop has 2Gb RAM and the memory meter shows 400/511.9 used. After awhile there's some garbage collection and memory usage goes down to about 100 but then creeps back up to 400 again. After completing scanning/compiling memory meter hovers around 387.5/511.9
Product Version: NetBeans IDE Dev (Build 200707230000) Java: 1.5.0_12; Java HotSpot(TM) Client VM 1.5.0_12-b04 System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb) Userdir: C:\Documents and Settings\JohnBaker\.netbeans\dev
Let me separate two issues here: -the amount of memory consumed during initial scan: I do not think the Java infrastructure can affect this very much. The initial scan can run in very limited amount of memory, but can use more memory if available to speed up the process. But, in your case, I would estimate than most of the consumed memory is not-reclaimed reclaimable garbage (thrown away instances of javac, etc.). I assume than when the initial scan finishes and you press the GC button, the used memory drops to some reasonable number. So this seems to be caused more by high mx (which is 512MB in your case), then by the Java infrastructure itself. -the length of the scanning process: please note that we need to scan/compile not only the visualweb/dataconnectivity module, but also all its dependencies, recursively. Please note that only the very first scan is slow - the subsequent ones should be much faster.
The issue, as stated is invalid. Source modeling it not consuming that much memory and the fact that memory meter displays large number doesn't mean that the IDE needs that much memory. The relevant number is the number after explicit GC, and that would be much smaller.