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.
I'm running NB 5.0 on Win XP Pro Pentium 4 with Hyperthreading Technology and 1 GB of RAM. Everytime I do a "Find" (on the context menu in either the Projects or Files window), I get a message saying that the search "prematurely stopped due to reaching current memory limit." What is going on? Also, the Find feature doesn't seem to be able to find a file that actually exists even if I type in the exact name. I typed in "config.xml", and it never finds it. I even try doing the search directly on the folder that contains the file, and it still does not find the file. I've tried searching using both the "Full Text" tab and the "Object Name" tab, and I get the same problem. How hard can it be to use NetBeans to find a file? Eclipse has an Open Resource window that finds as you type, and the results appear immediately (even with the thousands of files in my project). Can NetBeans not do the same?
The message about memory limit is emitted by a low-memory detector routine built in the search feature. It means that the usage of the Java heap is close to its limits so that the search feature stopped itself to prevent the JVM from going out of memory. The current detection mechanism is not ideal and could be replaced by the standard memory management API, now that we have switched to JDK 1.5; I just filed an issue for this - see issue #79977. The problem with searching by name is a known issue and a bug report has been filed just a month ago - see bug #71301 ("Object Name in Find in Projects dialog is misleading"). In brief, object name is a file name without an extension. To find 'config.xml', enter just 'config' as an object name. *** This issue has been marked as a duplicate of 71301 ***