|
| Re: Potential Locking Issue on Project Import [message #753914 is a reply to message #753890] |
Sun, 30 October 2011 10:53  |
Eclipse User |
|
|
|
Marcel Bruch skrev 2011-10-30 08.5820:
> Hi,
>
> I just created a fresh workspace and imported all Eclipse projects from a git repository. During the import, Eclipse got stuck. I could terminate the import by pressing the
> cancel button on the import wizard page. On my second try (and deleting the already existing project from workspace), the import successfully completed. To me it looks like
> that there was a locking issue w/ the workspace. But that's just a wild guess :)
>
> I'm unfortunately not able to reproduce this one - but maybe you guys know where to look for this issue. The stacktrace EGit wrote into the log file after interruption,
> looks as follows:
>
> java.lang.InterruptedException
> at org.eclipse.egit.ui.internal.clone.ProjectUtils.createProjects(ProjectUtils.java:86)
> at org.eclipse.egit.ui.internal.clone.GitImportWizard.importProjects(GitImportWizard.java:160)
> at org.eclipse.egit.ui.internal.clone.GitImportWizard.access$0(GitImportWizard.java:142)
> at org.eclipse.egit.ui.internal.clone.GitImportWizard$1.run(GitImportWizard.java:83)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
>
>
> Let me know if this should be filed and tracked in Bugzilla.
>
> Thanks, Marcel
If you believe this is a bug, please report it. Any reasonable event, i.e. something the user
does using Eclipse only should be possible to resolve. Even rare events, that are hard to
reproduce are bugs. Hard-to-reproduce bugs may not be fixed.
You can get a stack trace before you abort using jvisualvm or jstack. Add it to the bug report.
-- robin
|
|
|
Powered by
FUDForum. Page generated in 0.02641 seconds
Home
