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 use favorites to search a file by name across two mapped drives C: and D: . I do this because I want to use a GUI not a command line (as required in Windows 7) to do simple searches. I just enter the file name (no text content) to make the search fast, hoping that the IDE does not open the files. After an hour of consuming almost 100% CPU, the IDE stops responding and I have to kill it in task manager. From my perspective, this is unacceptable behavior. If the IDE cannot do this, then it must tell me it can't - not crash.
Attach a thread dump when the IDE freezes.http://wiki.netbeans.org/GenerateThreadDump
Will try thread dump later. Meanwhile I uploaded a heap dump, http://deadlock.netbeans.org/job/upload/ build #507. The uploaded zip file contains the entire log directory.
My apologies. I tried to reproduce this without luck, therefore I cannot provide a thread dump. I remember that during the search, I deleted a directory containing found files. Perhaps this delete action caused the issue. I tried this deletion again without luck. Meanwhile it is good to know that the IDE is quite capable to search entire drives normally without failing. Perhaps the heap dump can provide some answers?
(In reply to bht from comment #3) > My apologies. I tried to reproduce this without luck, therefore I cannot > provide a thread dump. No problem at all. > I remember that during the search, I deleted a directory containing found > files. Perhaps this delete action caused the issue. It could have affected the memory consumption. > I just enter the file name (no text content) to make the search fast, hoping > that the IDE does not open the files. The files are not opened when searching in this case, but if the file name matches, some file contents may be read to get exact MIME-type, to choose a correct icon for it, or to detect versioning status. So if a lot of matching files is found, the memory consumption (and I/O activity) can be very high. And it seems probable when searching in the whole hard drive. > I tried this deletion again without luck. Meanwhile it is good to > know that the IDE is quite capable to search entire drives normally without > failing. Perhaps the heap dump can provide some answers? I cannot find anything suspicious in the heap dump, but I'm still running the analysis. Thank you for help.
> I cannot find anything suspicious in the heap dump, but I'm still running > the analysis. The analysis didn't show any useful information, so I'm leaving this issue closed. Thank you.