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 242158

Summary:	"closing native projects" delays ide exit by 15-20 seconds
Product:	cnd	Reporter:	tbrunhoff <tbrunhoff>
Component:	Code Model	Assignee:	Maria Tishkova <mromashova>
Status:	NEW ---
Severity:	normal
Priority:	P3
Version:	8.0
Hardware:	PC
OS:	Linux
Issue Type:	DEFECT	Exception Reporter:
Attachments:	list of files modified by first run of described test list of files modified by second run of described test list of files modified by third run of described test list of files modified by running with no projects open.

Description tbrunhoff 2014-02-20 15:58:51 UTC

Running the version below, every time I exit the ide, I get the small "closing native project" status bar for about 15-20 seconds. My machine is an i7 w/ 32 GB of memory and 6TB in raid 5.

Product Version: NetBeans IDE Dev (Build 201402040001)
Java: 1.7.0_45; Java HotSpot(TM) Client VM 24.45-b08
Runtime: Java(TM) SE Runtime Environment 1.7.0_45-b18
System: Linux version 3.12.6-200.fc19.x86_64 running on i386; UTF-8; en_US (nb)
User directory: /home/toddb/.netbeans/dev
Cache directory: /home/toddb/.cache/netbeans/dev

Comment 1 Alexander Simon 2014-02-21 19:38:09 UTC

It is expected behavior. Since 8.0 C/C++ informs user that closing (writing unsaved data) in progress.
Please explain what is a problem?

Comment 2 tbrunhoff 2014-02-21 20:50:36 UTC

This particular machine can write well over 100MB/sec, reliably. The performance appears to have a linear relationship to the number of projects open.  I currently have 25 open when the IDE starts. Most of the projects are small (one directory, 5-20 files).

For me:
1: start ide
2: wait for background scanning of projects to complete
3: stop ide
4: wait 15-20 seconds while java burns about 10-15% of cpu and rewrites 500-1100 files.

I did three tests. I had 25 projects open that looked like this:
    $ touch junk
    < steps 1-4 above >
    $ find ~/.netbeans ~/.cache/netbeans . -type f -newer junk -print0 \
      | xargs -0 ls -l > 12:30.files

I've attached the output from these tests. If I rerun the tests with zero or one projects open, it closes quickly, but still finds it necessary to write ~270 files.

So that is expected behavior?

Comment 3 tbrunhoff 2014-02-24 20:58:12 UTC

Created attachment 145553 [details]
list of files modified by first run of described test

Comment 4 tbrunhoff 2014-02-24 20:58:34 UTC

Created attachment 145554 [details]
list of files modified by second run of described test

Comment 5 tbrunhoff 2014-02-24 20:59:00 UTC

Created attachment 145555 [details]
list of files modified by third run of described test

Comment 6 tbrunhoff 2014-02-24 21:00:11 UTC

Created attachment 145556 [details]
list of files modified by running with no projects open.

Comment 7 pwade 2014-10-21 22:56:03 UTC

Having similar issue but Closing native projects... bar never disappears.  Waited up to 5 minutes.  No CPU usage shown by NetBeans.  Had to end task to get it to close.  I only have one C++ project and it only has 2 source files.  Not sure if this should be a new issue or not.

Comment 8 Alexander Simon 2014-10-22 06:57:18 UTC

(In reply to pwade from comment #7)
> Having similar issue but Closing native projects... bar never disappears. 
> Waited up to 5 minutes.  No CPU usage shown by NetBeans.  Had to end task to
> get it to close.  I only have one C++ project and it only has 2 source
> files.  Not sure if this should be a new issue or not.
It is another problem.
If you have a reproducible scenario, please file a bug with attached thread dump (see http://wiki.netbeans.org/GenerateThreadDump).