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 222728 - Performance problems when C/C++ plugin used
Summary: Performance problems when C/C++ plugin used
Status: CLOSED INCOMPLETE
Alias: None
Product: cnd
Classification: Unclassified
Component: Project (show other bugs)
Version: 7.2
Hardware: PC Linux
: P2 normal (vote)
Assignee: Alexander Simon
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-26 02:12 UTC by ionuion
Modified: 2013-08-08 20:33 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ionuion 2012-11-26 02:12:40 UTC
Users on the #netbeans IRC channel report severe performance problems when using the C/C++ plugin. 
Following two descriptions:

User 1 (fr**y):

Environment:
Product Version: NetBeans IDE 7.2.1 (Build 201210100934)
Java: 1.6.0_24; OpenJDK 64-Bit Server VM 20.0-b12
System: Linux version 3.6.6-1-ARCH running on amd64; ANSI_X3.4-1968; en_US (nb)
User directory: /home/a**w/.netbeans/7.2.1
Cache directory: /home/a*w/.cache/netbeans/7.2.1
GCC version: 4.7.2-2
4-cores Intel core i7 CPU

Behavior:
NetBeans IDE using 100% of all 8 CPU threads

In the logs:
WARNING [org.openide.awt.Toolbar]: Too long AWTTask: 11,890 ms for org.openide.awt.MenuBar$LazyMenu$MenuFolder@6000fb42(FolderList{MultiFileObject@71591b4d[Menu/Window]})



User 2 (l**r)

Environment:
NetBeans 7.2
C/C++ plugin, 
Java 7, 
64bit x86 
4gb ram

Behavior:
'after some time i use it the java process behind the ide starts to eat all the cpu'
'parsing a simple project requires 2 mins'

In the logs:
WARNING [org.netbeans.core.TimableEventQueue]: too much time in AWT thread org.netbeans.modules.sampler.InternalSampler@336ade6b

Please let me know what further information can aid in solving the problem.
Thank you.
Comment 1 Leonid Lenyashin 2012-11-26 06:07:06 UTC
First we need to check if it isnt something we fixed in 7.3 and limit number of parsing threads down to 4.
Sasha, please, investigate.
Comment 2 Alexander Simon 2012-11-26 07:41:32 UTC
Please provide additional info. It can be:
- slowness report
- threads dump at the time when IDE eat 100% of 8 threads
- IDE profiling snap shot.

Thanks,
Alexander
Comment 3 ionuion 2013-08-08 20:33:33 UTC
Closing, as the users reporting the issues have not been present on the IRC channel, so the required artifacts cannot be provided.