Community
Participate
Working Groups
Build Identifier: 20110301-1815 Working in a workspace with more than one project inside i modify some file on a project (that doesn't have a git repository associated) and i don't save the file that i'm working on, then i select another project in Package explorer(this project have a git repository associated) and right click on it then Team menu and click on push, at this point eclipse ask to me if i want to save the file that i've modified before, i respond Yes. After this procedure Eclipse SDK remain completely frozen, the application doesn't respond and i have to kill it with task manger. However i don't understand neither why eclipse ask for saving the file that is not a file of the project which push is executed. Reproducible: Always Steps to Reproduce: 1. Modify a file in a project (that doesn't have a git repository) 2. Without saving the file, select another project(that have a git repository) and from team menu push the changes 3. When eclipse prompt for saving the file select Yes
Created attachment 205326 [details] Error reopening Eclipse after the freeze. After reopening the project i get this error.
(In reply to comment #0) > After this procedure Eclipse SDK remain completely frozen, the application > doesn't respond and i have to kill it with task manger. So the UI doesn't repaint itself anymore? Or can you still click around? If you can reproduce the problem, can you attach a thread dump to this bug? wiki.eclipse.org/index.php/How_to_report_a_deadlock
Created attachment 205383 [details] Thread dump
Created attachment 205384 [details] UI screenshot
The UI is completely frozen and i can't click around because the application doesn't respond anymore ... I can reproduce the problem any time that i follow the procedure that i listed in the Steps to reproduce section, I've uploaded a Thread Dump and a screenshot of the UI, let me know if you need something else ... I'm on JDK 7 ...
(In reply to comment #3) > Created attachment 205383 [details] > Thread dump Alessio, please open a bug with Aptana. You are not using EGit but Aptana's own Git plug-in.