Community
Participate
Working Groups
I using Eclipse 4.4 RC1 to developer OFBiz application. When i work with 4.3.2: everything are ok, but with 4.4 RC1: when i start OFBiz application, the CPU usage of Eclipse always greater than 25%.
https://www.eclipse.org/eclipse/platform-text/development/bug-incomplete.htm
I start OFBiz application by Ant build tool, when i set up JRE for Ant with option "Separate JRE" and chose the difference one, the problem will come as i described. When "Run in the same JRE as the workspace" => no issue. But the issue does not occur on Eclipse 4.3.*
(In reply to Rong Nguyen from comment #2) > I start OFBiz application by Ant build tool, when i set up JRE for Ant with > option "Separate JRE" and chose the difference one, the problem will come as > i described. > When "Run in the same JRE as the workspace" => no issue. > > But the issue does not occur on Eclipse 4.3.* Please make several stack traces while the CPU is high and then attach them here.
We can't do anything without further information.
Sorry for slow response. Now, i run Eclipse 4.4.2 RC2 and the application is Apache OFBiz. My flatform: - OS: Fedora 21 - Java: Sun JSK 1.6.45 I don't see any "stack traces while the CPU is high" or anything else!
(In reply to Rong Nguyen from comment #5) > I don't see any "stack traces while the CPU is high" or anything else! Please refer to this page on reporting performance problems with eclipse: https://wiki.eclipse.org/How_to_report_a_deadlock And share the details here.
(In reply to Jay Arthanareeswaran from comment #6) > (In reply to Rong Nguyen from comment #5) > > I don't see any "stack traces while the CPU is high" or anything else! > > Please refer to this page on reporting performance problems with eclipse: > > https://wiki.eclipse.org/How_to_report_a_deadlock > > And share the details here. Thanks you the the reply, 1. What build of Eclipse you are using (see Help > About): - Build id: 20150219-0600 2. What VM you are using (version and vendor). Use "java -version" to find out version information. - java version "1.6.0_45" Java(TM) SE Runtime Environment (build 1.6.0_45-b06) Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01, mixed mode) 3. What you were doing at the time of the deadlock (what dialog, wizard, editor, etc) - Just start Apache OFBiz application by selecting 'start-debug' ant task. 4. Your JVM configuration: how much memory is being allocated to the JVM - 4GB 5. Your machine configuration: how much RAM, how much RAM is free, was it swapping - RAM: 8GB, 5GB is free, 8GB swap 6. Whether it is reproducible; if so, provide steps -There is no stack trace.
Thanks, this gives a start but no hint yet regarding the actual cause of your problem. (In reply to Rong Nguyen from comment #7) > 6. Whether it is reproducible; if so, provide steps > -There is no stack trace. Have you tried to follow the advice on getting a stack trace in https://wiki.eclipse.org/How_to_report_a_deadlock ? By "steps" we mean a list of instructions how we could replay the problem on our side: what do we need to do in order to run into the same problem?
Sorry for late reply. I can not create enough steps in your link. The following steps is the step which caused the error: 1. Download any version of OFBiz in this link: https://ofbiz.apache.org/ 2. Import OFBiz project to Eclipse. 3. Drag build.xml file to ant window. 4. Find "start-debug" task. 5. Right mouse to choose the JRE configuration to start ant task 6. In JRE tab, choose: "Separate JRE"(pick any jre version) 7. Execute "start-debug" task 8. See the CPU is very high. Now, I have to choose "Run in the same JRE as the workspace", but this option can not run others task, it only be done in console... Thank you again for the corporation :-)
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
