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.

Bug 192968 - High CPU usage by File Watcher
Summary: High CPU usage by File Watcher
Status: RESOLVED DUPLICATE of bug 192427
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 7.0
Hardware: PC Linux
: P2 normal (vote)
Assignee: Jaroslav Tulach
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-07 12:30 UTC by Tomas Mysik
Modified: 2010-12-07 13:11 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
profiler snapshot (11.67 KB, application/octet-stream)
2010-12-07 12:30 UTC, Tomas Mysik 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tomas Mysik 2010-12-07 12:30:25 UTC 
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)
Comment 1 Jaroslav Tulach 2010-12-07 12:59:34 UTC 
Č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 ***
Comment 2 Tomas Mysik 2010-12-07 13:05:42 UTC 
(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.
Comment 3 Tomas Hurka 2010-12-07 13:11:31 UTC 
(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.