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.
Twice today while performing a substring Find-In- Files search of a medium-sized codebase on a machine with 128mb RAM, Netbeans has frozen up and I have needed to restart. The first time, I was running with heap size set to 80mb, and the search process kicked off disk thrashing that lasted 25 mins, without an end! Later on, having extended the heap back to the 96 default, I did another search which only caused moderate disk activity, but consumed 100% CPU. I successfully pressed "Stop search" button a few times but the search didnt terminate after 5 mins. I was not able to find anything relevant in the IDE logfile, eg related stack traces. Seems that something is running out of control, or is the search process generating a stream of garbage that is causing the GC to thrash on this low memory machine?
This is a duplicate of bug #19484 - "OOME when performing search on larger FS". See also bug #41445 - "search on disk root seems to be leaking memory even when no matching item was found". *** This issue has been marked as a duplicate of 19484 ***