Bug 516742 - Eclipse CPU usage is way more than 100% on Mac OS X El Capitan (10.11.6) with Java 1.8.0_131 when multi module maven projects are opened
Summary: Eclipse CPU usage is way more than 100% on Mac OS X El Capitan (10.11.6) wit...
Status: NEW
Alias: None
Product: JSDT
Classification: WebTools
Component: General (show other bugs)
Version: unspecified   Edit
Hardware: Macintosh Mac OS X
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Victor Rubezhny CLA
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2017-05-16 12:53 EDT by Nabi Zamani CLA
Modified: 2019-01-31 12:58 EST (History)
3 users (show)

See Also:


Attachments
jstack dumps (158.80 KB, application/zip)
2017-05-25 09:52 EDT, Nabi Zamani CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nabi Zamani CLA 2017-05-16 12:53:37 EDT
When I open Eclipse Java EE x64 on Mac OS X El Capitan (10.11.6) then the CPU consumption goes crazy while I actually do nothing. The CPU consumption stays high as long as Eclipse is running, which means that my Mac's fan goes crazy very soon after Eclipse is started. Furthermore, the only way to exit Eclipse is by killing the process because closing Eclipse the normal way will hide the window but Eclipse never stops.

I have the latest Glassfish Tools installed from the marketplace. Other than that I have a multi module maven project: ear, ejb, jar, war. I have just now discovered that when I close the projects then eclipse keeps working just fine - so there is no high CPU consumption then. As soon as I open the projects the CPU usage rapidly increases and I have the same issues again… I always have to kill eclipse and I typically send the crash repots to Apple…

I have also tried to uninstall the Glassfish Tools and see what happens, but I cannot see any change at all - so the Glassfish Tools are not causing the issue. I have also downloaded Eclipse again and again and I always used clean workspaces. However, even this did not help. My colleague has the same issue on his MacBook Pro 2016 with the latest version of macOS and using the same multi module maven project. This makes me believe that there is some other issue with the „out of the box“ Eclipse Java EE package which is related to multi module maven projects. Because of this Eclipse is not usable for us (we’re using other IDEs for now). Unfortunately, I cannot easily offer you our maven project...

Any idea? I tried everything I have no clue what else I should try.




-- Configuration Details --
Product: Eclipse 4.6.3.20170314-1500 (org.eclipse.epp.package.jee.product)Installed Features:
 org.eclipse.jdt 3.12.3.v20170301-0400
Versioning Plugin:
 org.eclipse.platform 4.6.3.v20170301-0400
Comment 1 Andrey Loskutov CLA 2017-05-16 13:02:31 EDT
Please create few jstack dumps while Eclipse is busy and attach them here.
Comment 2 Nabi Zamani CLA 2017-05-25 09:52:34 EDT
Created attachment 268566 [details]
jstack dumps

I just attached the stack dumps. I took them for 2 different situations:
1. I opened eclipse and while doing exactly nothing 
2. Closing Eclipse (i.e. with Cmd + q)
Comment 3 Giovanni Lovato CLA 2019-01-31 11:07:30 EST
I'm experiencing the same symptoms with Eclispe 2018-12 and macOS Mojave on a MacBook Pro (2018). Also, the MacBooks fans go crazy and never stops; battery drains quickly. How can I create jstack dumps to attach them here?
Comment 4 Stephan Herrmann CLA 2019-01-31 12:57:35 EST
(In reply to Nabi Zamani from comment #2)
> Created attachment 268566 [details]
> jstack dumps
> 
> I just attached the stack dumps. I took them for 2 different situations:
> 1. I opened eclipse and while doing exactly nothing 
> 2. Closing Eclipse (i.e. with Cmd + q)

I looked at a few samples and found JDT idle. By contrast, JSDT looks busy:

"JavaScript indexing" #32 daemon prio=4 os_prio=31 tid=0x0000000121b7f800 nid=0xfb1f runnable [0x000070000227f000]
   java.lang.Thread.State: RUNNABLE
	at org.eclipse.wst.jsdt.internal.compiler.ast.ListExpression.<init>(ListExpression.java:47)
	at org.eclipse.wst.jsdt.internal.compiler.parser.Parser.consumeListExpression(Parser.java:2780)
	at org.eclipse.wst.jsdt.internal.compiler.parser.Parser.consumeRule(Parser.java:3261)
	at org.eclipse.wst.jsdt.internal.compiler.parser.Parser.parse(Parser.java:5810)
	at org.eclipse.wst.jsdt.internal.compiler.parser.Parser.parse(Parser.java:6044)
	at org.eclipse.wst.jsdt.internal.compiler.parser.Parser.parse(Parser.java:5996)
	at org.eclipse.wst.jsdt.internal.compiler.SourceElementParser.parseCompilationUnit(SourceElementParser.java:1449)
	at org.eclipse.wst.jsdt.internal.core.search.indexing.SourceIndexer.indexDocument(SourceIndexer.java:92)
	at org.eclipse.wst.jsdt.internal.core.search.JavaSearchParticipant.indexDocument(JavaSearchParticipant.java:79)
	at org.eclipse.wst.jsdt.internal.core.search.indexing.IndexManager.indexDocument(IndexManager.java:351)
	at org.eclipse.wst.jsdt.internal.core.search.indexing.IndexManager$1.execute(IndexManager.java:754)
	at org.eclipse.wst.jsdt.internal.core.search.processing.JobManager.run(JobManager.java:393)
	at java.lang.Thread.run(Thread.java:748)


=> moving
Comment 5 Stephan Herrmann CLA 2019-01-31 12:58:21 EST
(In reply to Giovanni Lovato from comment #3)
> I'm experiencing the same symptoms with Eclispe 2018-12 and macOS Mojave on
> a MacBook Pro (2018). Also, the MacBooks fans go crazy and never stops;
> battery drains quickly. How can I create jstack dumps to attach them here?

see https://wiki.eclipse.org/How_to_report_a_deadlock