Community
Participate
Working Groups
We are facing below issues when using Eclipse Mars with E-Git,we have around 70 packages in our project and around 1000 files. 1) Slowness issue while working when switch between the files or use any shortcut key like Ctrl+O. 2) Sometimes work space got hanged while working and need to kill process through Task Manger. 3)The Major issue is when we save data and it does not show compilation issues.It shows errors after building worksapce. Is these issues are specific with Eclipse Mars or problem is with E-Git or any other? Please provide any suggestions.
4.5.2 is not supported anymore. Please try latest official 4.9 release or check for commercial help.
Eclipse 2018-09 will be much faster. Please reopen if that is still reproducible.
Thanks for the response.Now we are using Eclipse Photon Release(4.8.0) and having better experience but still slowness issue is there and it is taking some time around 10-12 seconds to show compilation errors. Is there any settings in eclipse ,we can do to avoid these issue and speed up Eclipse?
(In reply to Anjali Jain from comment #3) > Thanks for the response.Now we are using Eclipse Photon Release(4.8.0) and > having better experience but still slowness issue is there and it is taking > some time around 10-12 seconds to show compilation errors. > Is there any settings in eclipse ,we can do to avoid these issue and speed > up Eclipse? I could give it to you if you would provide few jstack dumps at time Eclipse is "slow". Deal?
Please also consider to switch to 4.9.0, 4.8.0 is not supported anymore. Also please check if 4.10 RC1 is faster for you, we had few fixes there too.
https://www.eclipse.org/eclipse/platform-text/development/bug-incomplete.htm
Created attachment 276902 [details] Thread dumps when did changes in file to see compilation error I did some changes in java file so that compilation will generate and at the same time captured Thread dumps using Java visualVM to see why its taking time to show compilation error in Eclipse.
Created attachment 276903 [details] Thread dumps when did changes in file to remove compilation error I did some changes in java file so that compilation error will remove and at the same time captured Thread dumps using Java visualVM to see why its taking time to show that compilation error got removed in Eclipse.
Attached Thread dumps as suggested, not sure they are helpful or not.Please have a look and let me know if some thing else is required. Thanks.
(In reply to Andrey Loskutov from comment #4) > (In reply to Anjali Jain from comment #3) > > Thanks for the response.Now we are using Eclipse Photon Release(4.8.0) and > > having better experience but still slowness issue is there and it is taking > > some time around 10-12 seconds to show compilation errors. > > Is there any settings in eclipse ,we can do to avoid these issue and speed > > up Eclipse? > > I could give it to you if you would provide few jstack dumps at time Eclipse > is "slow". Deal? Hi, I have attached some thread dumps when eclipse was slow and not showing compilation error.Can you please have a look.
One more information, its working five with small files.its taking time to show compilation errors with large files.
(In reply to Anjali Jain from comment #10) > Hi, > I have attached some thread dumps when eclipse was slow and not showing > compilation error.Can you please have a look. The UI thread idling in your dumps. I see nothing suspicious. Either those dumps are too late, or you've created them for a different Eclipse process (if you have many Eclipse running).
(In reply to Andrey Loskutov from comment #12) > (In reply to Anjali Jain from comment #10) > > Hi, > > I have attached some thread dumps when eclipse was slow and not showing > > compilation error.Can you please have a look. > > The UI thread idling in your dumps. I see nothing suspicious. Either those > dumps are too late, or you've created them for a different Eclipse process > (if you have many Eclipse running). Thanks.I tried one more time to capture dumps, May be this time they will be helpful. Attached the same.
Created attachment 276919 [details] Thread dumps when did changes in file to see compilation error Thread dumps when did changes in file to see compilation error
Created attachment 276920 [details] Thread dumps when did changes in file to remove compilation error-1 Thread dumps when did changes in file to remove compilation error
Am I correct that you have the issue with the editor and not with the error reporting on e.g. the Package Explorer?
(In reply to Dani Megert from comment #16) > Am I correct that you have the issue with the editor and not with the error > reporting on e.g. the Package Explorer? Yes.You are correct.
Looks like CompilationUnit.reconcile takes long. We would need to have a test case to investigate the issue.
(In reply to Dani Megert from comment #18) > Looks like CompilationUnit.reconcile takes long. > > We would need to have a test case to investigate the issue. Thanks.Please let me know what type of information should i share for that.
(In reply to Anjali Jain from comment #19) > (In reply to Dani Megert from comment #18) > > Looks like CompilationUnit.reconcile takes long. > > > > We would need to have a test case to investigate the issue. > > Thanks.Please let me know what type of information should i share for that. Either a workspace that allows to reproduce or steps starting with a fresh workspace. Do you always see the delay or just with some files?
(In reply to Dani Megert from comment #20) > (In reply to Anjali Jain from comment #19) > > (In reply to Dani Megert from comment #18) > > > Looks like CompilationUnit.reconcile takes long. > > > > > > We would need to have a test case to investigate the issue. > > > > Thanks.Please let me know what type of information should i share for that. > > Either a workspace that allows to reproduce or steps starting with a fresh > workspace. > > Do you always see the delay or just with some files? Yes,Its not for all files.For example the Bean files which have only setter and getter methods and the files in which only constants are declared, they are showing errors immediately.I think this problem is with the files which have heavy logic in it like interaction with other system(Database,webservicecall etc).
(In reply to Anjali Jain from comment #21) > > Do you always see the delay or just with some files? > > Yes,Its not for all files.For example the Bean files which have only setter > and getter methods and the files in which only constants are declared, they > are showing errors immediately.I think this problem is with the files which > have heavy logic in it like interaction with other > system(Database,webservicecall etc). That's what I presumed. We can't help without any test case.
(In reply to Dani Megert from comment #22) > (In reply to Anjali Jain from comment #21) > > > Do you always see the delay or just with some files? > > > > Yes,Its not for all files.For example the Bean files which have only setter > > and getter methods and the files in which only constants are declared, they > > are showing errors immediately.I think this problem is with the files which > > have heavy logic in it like interaction with other > > system(Database,webservicecall etc). > > That's what I presumed. We can't help without any test case. Ok. Actually due to some privacy, we can not share our workspace and its very big in size also.Not sure , but can we have a live interaction session with join me or skype, so that i can show the actual scenario?Is this possible?
(In reply to Anjali Jain from comment #23) > Ok. Actually due to some privacy, we can not share our workspace and its > very big in size also.Not sure , but can we have a live interaction session > with join me or skype, so that i can show the actual scenario?Is this > possible? I'm not sure this helps much. I believe that you see the problem. Maybe you can try to reproduce with a similar sized Java file and send us an obfuscated version?
