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.
Created attachment 98915 [details] threads.dump after several builds open cnd.modelimpl open cppparser.g file add space, press F11 => After modification of that file and pressing F11 I see + 2 never dying threads. I'm afraid after some builds threads limit can be reached... or OOM
I can reproduce at least. I feel like there is a bug in NbIO, since IOReader.close() is supposed to set inputClosed = true and also lock.notifyAll(), which should cause read(...) to stop waiting and return -1 immediately; I guess close() is just not getting called for some reason, though BridgeImpl.run explicitly seems to be doing so.
...and when I go through it in a debugger, the reader thread does in fact exit as expected due to the call to close(). Yet other similar reader threads still seem to be waiting until interrupted. Don't know how to explain.
core-main #2f41152dbaf3