Community
Participate
Working Groups
Build Identifier: M20110210-1200 First of all, just let me say that I am not sure that Eclipse is the guilty one, it could be Clearcase or the TITAN plugin, but I need help locating the source to this problem. Eclipse used to work acceptably fast, but recently things has been going very slow. Every character I type in triggers the eclipse.exe to jump up to 50% CPU usage (on a dual core, so I guess it occupies a single core to 100%) and this last for at least 10 sec. Which means that simply coding in the editor keeps my CPU fan running on high pitch while writing. Also, the memory monitor in the lower right corner jumps like crazy between 700-1200 MB while typing. The most annoying thing are the intermittent lock-ups where Eclipse simply stops responding. Eclipse were more or less useless until I got support with increasing the heap size to 1200 MB (I cannot increase it more, Vista 32 and 4 GB), now it is just _very annoying. Things get better if I turn of the on-the-fly-checker in TITAN preferences, but then I lose functionality I need, such as F3, outline and code completion. Pls see attached documents for a list of plugins and error reports. Reproducible: Always
Created attachment 196084 [details] Configuration from Eclipse
Created attachment 196085 [details] Error report from Eclipse
Created attachment 196086 [details] Screen shot of task mgr during editing
The issues that you have described indicate that the TITAN plugin is guilty. I do not know what it does, but could you uninstall it and check if things got better? Also, you could gather javacores, so we could check exactly what are the CPU cycles wasted for. Anyway, I expect this issue is not related to Eclipse at all.
Hi, I did a complete re-install a few weeks ago, upgraded to current Eclipse version and re-installed the plugins, but with no difference in performance. How do I gather javacores? BR, Andreas (In reply to comment #4) > The issues that you have described indicate that the TITAN plugin is guilty. I > do not know what it does, but could you uninstall it and check if things got > better? > Also, you could gather javacores, so we could check exactly what are the CPU > cycles wasted for. > Anyway, I expect this issue is not related to Eclipse at all.
In which editor do you edit? If it is an editor from Eclipse SDK, do you also see the problem with plain Eclipse SDK (no Clearcase and no TITAN installed)?
Now you're asking difficult questions :) I use the standard setup at Ericsson, an editor within Eclipse, its preferences are under Preferences/Java/Editor, so somehow it is related to Java. I am sorry, I am just a user of Eclipse.
(In reply to comment #7) > I use the standard setup at Ericsson So do your other Ericsson colleagues face the same problem?
(In reply to comment #7) > Now you're asking difficult questions :) I use the standard setup at Ericsson, > an editor within Eclipse, its preferences are under Preferences/Java/Editor, so > somehow it is related to Java. I am sorry, I am just a user of Eclipse. In the Package Explorer select the file that causes problems when opened in the editor. Then open the context menu and select 'Open With'. Which editor has the black bullet?
Yes, they do, to various extents. It seems to be related to the project size they are working in, and people also use different eclipse.ini, with different settings of the RAM limits. I encountered the problem a month ago, other colleagues was affected earlier and some are not. But yes, there are alot of us facing this problem.
(In reply to comment #9) > editor. Then open the context menu and select 'Open With'. Which editor has the black bullet? It is called TTCN-3 Editor.
>How do I gather javacores? http://wiki.eclipse.org/index.php/How_to_report_a_deadlock
(In reply to comment #12) > >How do I gather javacores? > http://wiki.eclipse.org/index.php/How_to_report_a_deadlock Ok, I've tried to follow the wiki, with some modifications to suit my setup. I started Eclipse with the following line C:\Ericsson\E4E\eclipse.exe -vm /Java/JRE/bin -vmargs -XX:+HeapDumpOnOutOfMemoryError It locked up quite badly, and I got a file java_pid11804 in the Eclipse install lib: C:\Ericsson\E4E which I have attached.
Memory dump here: http://www.logicapplied.se/Eclipse/java_pid11804.zip
The report shows: One instance of "com.ericsson.titan.designer.parsers.ProjectSourceSyntacticAnalyzer$TemporalParseData[]" loaded by "com.ericsson.titan.designer" occupies 217'508'088 (83.79%) bytes. The memory is accumulated in one instance of "com.ericsson.titan.designer.parsers.ProjectSourceSyntacticAnalyzer$TemporalParseData[]" loaded by "com.ericsson.titan.designer". ==> you need to report the bug against Titan.
(In reply to comment #15) > The report shows: > One instance of > "com.ericsson.titan.designer.parsers.ProjectSourceSyntacticAnalyzer$TemporalParseData[]" > loaded by "com.ericsson.titan.designer" occupies 217'508'088 (83.79%) bytes. > The memory is accumulated in one instance of > "com.ericsson.titan.designer.parsers.ProjectSourceSyntacticAnalyzer$TemporalParseData[]" > loaded by "com.ericsson.titan.designer". > ==> you need to report the bug against Titan. Yes, I will contact them about this. Thanks alot guys!!
