Community
Participate
Working Groups
Build Identifier: I20111221-1500 I use Rational's ClearCase SCM Adapter 7.6.0v201105111445 for a long time and it worked fine. Since my second to last update about three or four days ago I doesn't any more. This is only the current state but it started some time earlier. I do not know exactly when but I think when I moved to eclipse 4.2 some menu items from the scm adapter plugin failed e.g. "edit view properties" or "find checkouts" ... Reproducible: Always Steps to Reproduce: 1. Connect to Rational ClearCase (CPU load - Intel Core 2 Duo - raises between 13% and 30% 2. click "update view" (CPU load raises to 50% and eclipse IDE does not respond any more) 3.
Is there anything in your error log? <workspace>/.metadata/.log? When the IDE stops responding, try and get a stack trace. See http://wiki.eclipse.org/index.php/How_to_report_a_deadlock PW
Created attachment 208910 [details] Stack traces started with "eclipse.exe -consolelog -debug" made 3 stack traces: - application started and workspace opened (no further action done) - waiting -> 1. stack trace - press toolbar button "Connect to Rational ClearCase" - waiting until CPU load and memory usage stabilizes (application still responding) -> 2. stack trace - press tollbar button "Update View" - waiting (CPU load increases to 50%, application does not respond any more) -> 3. stack trace
Created attachment 208911 [details] log file "workspace/.metadata/.log Log file to stack traces
Some remarks to the project's / workspace's structure The workspace folder is located at drive "D:\Views\workspace42" Two project trees (snapshots) are located at the same directory level in "D:\Views\Tree_1\Source\.." "D:\Views\Tree_2\Source\.." Four eclipse projects are located: "D:\Views\Tree_1\Eclipse42\Project_1" "D:\Views\Tree_1\Eclipse42\Project_2" "D:\Views\Tree_2\Eclipse42\Project_3" "D:\Views\Tree_2\Eclipse42\Project_4" The source folders of the eclipse project's are not located within the eclipse project's directory tree but linked (from snapshots) into the project.
Looks like there's some sort of an infinite loop going on. at org.eclipse.ui.internal.handlers.E4HandlerProxy.canExecute(E4HandlerProxy.java:50) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:228) at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:209) at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:123) at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.canExecute(HandlerServiceImpl.java:108) at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.canExecute(HandlerServiceImpl.java:91) at org.eclipse.ui.internal.MakeHandlersGo.isEnabled(MakeHandlersGo.java:117) at org.eclipse.core.commands.Command.isEnabled(Command.java:833) at org.eclipse.ui.internal.handlers.CommandLegacyActionWrapper.isEnabled(CommandLegacyActionWrapper.java:290) at com.rational.resourcemanagement.cmui.ClearCaseActionDelegate.internalSelectionChanged(ClearCaseActionDelegate.java:215) at com.rational.resourcemanagement.cmui.ClearCaseActionDelegate.selectionChanged(ClearCaseActionDelegate.java:415) at org.eclipse.ui.internal.handlers.ActionDelegateHandlerProxy.updateDelegate(ActionDelegateHandlerProxy.java:337) at org.eclipse.ui.internal.handlers.ActionDelegateHandlerProxy.setEnabled(ActionDelegateHandlerProxy.java:515) at org.eclipse.ui.internal.handlers.E4HandlerProxy.canExecute(E4HandlerProxy.java:50)
Caused by the changes in bug 366560 PW
I've released a fix for this for tonight's I build, I20120123-2200 http://git.eclipse.org/c/platform/eclipse.platform.ui.git/commit/?id=07da720f89aa2269d4f8035aa681a33d119dbeba Could you please test it with the CC SCM Adapter? The earlier, the better. PW
http://download.eclipse.org/eclipse/downloads/drops4/I20120123-2200/index.php should contain this fix. PW
