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.
| Summary: | NetBeans eats 100% CPU right after start (no indexing on background) | ||
|---|---|---|---|
| Product: | platform | Reporter: | Jan Becicka <jbecicka> |
| Component: | Filesystems | Assignee: | Jaroslav Havlin <jhavlin> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | exceptions_reporter, hair, thurka, tzezula |
| Priority: | P3 | ||
| Version: | 7.3 | ||
| Hardware: | Macintosh | ||
| OS: | Mac OS X | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Attachments: | .npss file attached from NetBeans | ||
|
Description
Jan Becicka
2013-07-17 08:42:24 UTC
Created attachment 137300 [details]
.npss file attached from NetBeans
.npss file
There are several threads. 1st) There is scanning (RepositoryUpdater.worker) - collecting files 9s and scanning 3.5s - seems OK after start. 2nd) There is heavily active EDT - doing some javascript UI update 3rd) There are 4 active versioning threads. Reassigning to versioning to evaluate. (In reply to comment #2) > There are several threads. > > 1st) There is scanning (RepositoryUpdater.worker) - collecting files 9s and > scanning 3.5s - seems OK after > start. BTW background scanning progress was not visible. Sorry wrong snapshot. In the attached snapshot there is lot's of fileCreated fileDeleted events (even reporter did no external change). No indexing or parsing. Most of time spent in FileUtil.isParentOf This issue could be related to bug 232640. *** Bug 233406 has been marked as a duplicate of this bug. *** *** Bug 225288 has been marked as a duplicate of this bug. *** Closing as duplicate of bug 232640. Hopefully thread dumps with thread names that contain more info will be useful. *** This bug has been marked as a duplicate of bug 232640 *** |