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: | High CPU usage by File Watcher | ||
|---|---|---|---|
| Product: | platform | Reporter: | Tomas Mysik <tmysik> |
| Component: | -- Other -- | Assignee: | Jaroslav Tulach <jtulach> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | fvogler, thurka |
| Priority: | P2 | ||
| Version: | 7.0 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Attachments: | profiler snapshot | ||
Čau. Why do you think it is the filewatcher? Yes, it has 5s CPU time, but that is more a bug of the snapshot (CCing Tomáš Hůrka) then real problem (the invocation count is 1, so the thread probably just sits in a native call). All I can see is a high activity in EDT. ~100 events being processed there. So if anything, there is a problem in the TimableEventQueue. Florian Vogler sent us a patch for TimableEventQueue recently, it might fix the problem. I'll mark this as a duplicate of #192427, but if you gain some more info, feel free to reopen. *** This bug has been marked as a duplicate of bug 192427 *** (In reply to comment #1) > Čau. Ahoj :) > Why do you think it is the filewatcher? Yes, it has 5s CPU time, but that > is more a bug of the snapshot (CCing Tomáš Hůrka) then real problem (the > invocation count is 1, so the thread probably just sits in a native call). Sorry, I did not investigate the snapshot, I just had a look at the CPU time. > All I can see is a high activity in EDT. ~100 events being processed there. So > if anything, there is a problem in the TimableEventQueue. Florian Vogler sent > us a patch for TimableEventQueue recently, it might fix the problem. > > I'll mark this as a duplicate of #192427, but if you gain some more info, feel > free to reopen. Thanks. (In reply to comment #1) > Čau. Why do you think it is the filewatcher? Yes, it has 5s CPU time, but that > is more a bug of the snapshot (CCing Tomáš Hůrka) then real problem (the > invocation count is 1, so the thread probably just sits in a native call). Right, it is in the native code and we have no information if it is running or not. From the context, it looks like it is not running. |
Created attachment 103665 [details] profiler snapshot I returned from lunch, switched back to NB and my CPU started to be very busy, I had to restart NetBeans. Please, have a look at the attached snapshot. Thanks. Product Version: NetBeans IDE Dev (Build 101206-109112b5e639) Java: 1.6.0_22; Java HotSpot(TM) 64-Bit Server VM 17.1-b03 System: Linux version 2.6.35-23-generic running on amd64; UTF-8; cs_CZ (nb)