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 258225 - The process "Checking for external changes" never completes
Summary: The process "Checking for external changes" never completes
Status: NEW
Alias: None
Product: platform
Classification: Unclassified
Component: Filesystems (show other bugs)
Version: 8.1
Hardware: Macintosh Mac OS X
: P3 normal with 2 votes (vote)
Assignee: Jaroslav Havlin
Depends on:
Reported: 2016-03-03 11:28 UTC by chakie
Modified: 2016-10-01 18:26 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Screenshot of immortal process (49.48 KB, image/png)
2016-03-03 11:33 UTC, chakie

Note You need to log in before you can comment on or make changes to this bug.
Description chakie 2016-03-03 11:28:06 UTC

Comment 1 chakie 2016-03-03 11:33:07 UTC
Nice. Pressing <enter> while editing the bug title submits the whole thing. Damn Bugzilla.


Netbeans constantly shows a "Checking for external changes" down in my window and it never completes nor disappears. I clicked it to see what it was and it somehow ended as suspended. Now it hangs there are suspended and I can't get rid of it. I can cancel the task, but it reappears after a few seconds. I suspected that the task was responsible for making the system fans scream for mercy, and sure enough netbeans consumed 600% of my CPU power. After entering the suspended state NB now constantly sucks 105% or so, even when I don't touch the whole thing. Clearly it died a bit internally.

See attached screenshot.
Comment 2 chakie 2016-03-03 11:33:38 UTC
Created attachment 158728 [details]
Screenshot of immortal process
Comment 3 Vladimir Voskresensky 2016-03-03 14:07:20 UTC
"Checking for external changes" activity is controlled by Tools->Options->Miscellaneous. On Files tab you can find "Enabled auto-scanning of sources"
It is responsible for checking if files were changed externally when you switch between NB and other apps.

Also snapshot can help us to analyze what's going on
Comment 4 chakie 2016-03-03 15:15:39 UTC
I had to restart NB to calm down the CPU. If I see the task running again I can try to suspend it and see if it dies again and then check the profiling. But suspending it somehow put it in a state where it still sucked CPU but never completed its task.
Comment 5 mihai 2016-09-30 09:09:53 UTC
Same problem for me (NB 8.2 RC):

Checking for external changes starts randomly and never completes. Canceling the task does not solve the problem, it reappears.

I've reported the issue on Bug 242623

Please see the attachments from that issue (npss file and prinscreens).
Comment 6 mihai 2016-10-01 18:26:44 UTC
until now, it looks like this is solving my problem: