Eclipse Community Forums: Newcomers » Merge failed -> eclipse stops responding -> killall eclipse -> broken workspace -> what

Home » Newcomers » Newcomers » Merge failed -> eclipse stops responding -> killall eclipse -> broken workspace -> what (Eclipse stopped resonding when I tried to svn merge branch to trunk, had to kill it, now eclipse always stops responding after startup.)

Show: Today's Messages :: Show Polls :: Message Navigator

Merge failed -> eclipse stops responding -> killall eclipse -> broken workspace -> what [message #486876]

Sun, 20 September 2009 15:38

Timo

Messages: 2
Registered: September 2009

Junior Member

I treid to merge a branch to a trunk (or more like tried to figure out how to do it). This somehow failed and eclipse stopped responding. If I remeber right it was trying to resolve the path and/or revision or something and nothing seemed to happen. I pressed cancel, but as usual it had no effecet (I don't remeber ever pressing cancel so that it would have actually cancelled something, it always continues to deadlock). As cpu usage was near to 0, it was clear that eclipse wasn't really doing anything. So I was forced to kill eclipse. If I remeber right I had to say killall -9 eclipse to end the process. Now, after this episode, when ever I start eclipse it hangs. It starts, pops up the gui, showing me some code I had open. It even responds for a couple of seconds, but then it starts to do something and eclipse stops to respond. Once again it doesn't use any cpu so it's not really doing anything, but rather deadlocking or something. Now if I start eclipse with the cmd trigger -data /some/other/workspace it pops up just fine and wont hang. From this I figured eclipse had somehow broke my workspace.

Now my question is what to do? I found some help on how to get things working again:
http://wiki.eclipse.org/FAQ_How_can_I_repair_a_workspace_tha t_is_broken%3F
It suggests that I should file a bug report. Now if I file that above mentioned story as a bug report I doubt it'll have any effect. I doubt anybody can reproduce anything with it. If I'd have some logs, dumbs, etc. that might help a bit... anybody has any hints on how to turn this into a identifiable, possibly reproducable and most importantly fixable bug report? Oh and one more thing: which category? Platform? JDT?

P.S. Some additional information:
OS:
Linux, ubuntu 8.10, custom installation (not through apt-get)
eclipse version:
Eclipse IDE for Java Developers 1.2.0.20090619-0620
Eclipse Platform 3.5.0.I20090611-1540
SVN:
Subversive SVN Connectors 2.2.1.I20090708-1500
SVNKit 1.3.0 Implementation (Optional) 2.2.1.I20090708-1500
The project also uses maven.
Maven and svn (cmd) are (also not throgh apt-get):
Apache Maven 2.2.1 (r801777; 2009-08-06 22:16:01+0300)
svn, version 1.6.5 (r38866)
Java:
timo@timo-laptop:~$ java -version
java version "1.6.0_10"
Java(TM) SE Runtime Environment (build 1.6.0_10-b33)
Java HotSpot(TM) Client VM (build 11.0-b15, mixed mode, sharing)

[Updated on: Sun, 20 September 2009 15:49]

Report message to a moderator

Re: Merge failed -> eclipse stops responding -> killall eclipse -> broken workspace -> w [message #486924 is a reply to message #486876]

Mon, 21 September 2009 04:52

Walter Harley

Messages: 847
Registered: July 2009

Senior Member

"Timo" <sipulimaili@yahoo.co.uk> wrote in message
news:h95i9v$h6m$1@build.eclipse.org...
>I treid to merge a branch to a trunk (or more like tried to figure out how
>to do it). This somehow failed and eclipse stopped responding. If I remeber
>right it was trying to resolve the path and/or revision or something and
>nothing seemed to happen. I pressed cancel, but as usual it had no effecet
>(I don't remeber ever pressing cancel so that it would have actually
>cancelled something, it always continues to deadlock). As cpu usage was
>near to 0, it was clear that eclipse wasn't really doing anything. So I was
>forced to kill eclipse. If I remeber right I had to say killall -9 eclipse
>to end the process. Now, after this episode, when ever I start eclipse it
>hangs. It starts, pops up the gui, showing me some code I had open. It even
>responds for a couple of seconds, but then it starts to do something and
>eclipse stops to respond. Once again it doesn't use any cpu so it's not
>really doing anything, but rather deadlocking or something. Now if I start
>eclipse with the cmd trigger -data /some/other/workspace it pops up just
>fine and wont hang.
>
> Now my question is what to do? I found some help on how to get things
> working again:
> http://wiki.eclipse.org/FAQ_How_can_I_repair_a_workspace_tha t_is_broken%3F
> It suggests that I should file a bug report. Now if I file that above
> mentioned story as a bug report I doubt it'll have any effect. I doubt
> anybody can reproduce anything with it. If I'd have some logs, dumbs, etc.
> that might help a bit... anybody has any hints on how to turn this into a
> identifiable, possibly reproducable and most importantly fixable bug
> report? Oh and one more thing: which category? Platform? JDT?

I don't have the link offhand, but there is a page somewhere on eclipse.org
that talks about how to debug Eclipse hangs - basically, how to get a thread
dump that will let the Eclipse devs know what is waiting for what. There is
also an article on branching and merging with CVS in Eclipse - again, I
don't have the link handy, don't remember if it was in Help or if it's in
Eclipse Corner.

It will help if you specify what version control system you're using (CVS?
SVN? Perforce?), what version of Eclipse, what operating system, what
JRE... you might want to take a look at
http://catb.org/~esr/faqs/smart-questions.html for tips on what information
would be helpful in reporting the bug. Some other things you might want to
try are looking in the Eclipse error log to see if anything useful is
getting reported there, and running eclipse -clean and/or eclipse -debug to
see if those help.

Personally, since it works with other workspaces, my suggestion would be to
just delete and re-create that workspace (re-import the projects).

Report message to a moderator

Re: Merge failed -> eclipse stops responding -> killall eclipse -> broken workspace -> w [message #486963 is a reply to message #486924]

Mon, 21 September 2009 10:47

Dani Megert

Messages: 3802
Registered: July 2009

Senior Member

Walter Harley wrote:
> "Timo" <sipulimaili@yahoo.co.uk> wrote in message
> news:h95i9v$h6m$1@build.eclipse.org...
>
>> I treid to merge a branch to a trunk (or more like tried to figure out how
>> to do it). This somehow failed and eclipse stopped responding. If I remeber
>> right it was trying to resolve the path and/or revision or something and
>> nothing seemed to happen. I pressed cancel, but as usual it had no effecet
>> (I don't remeber ever pressing cancel so that it would have actually
>> cancelled something, it always continues to deadlock). As cpu usage was
>> near to 0, it was clear that eclipse wasn't really doing anything. So I was
>> forced to kill eclipse. If I remeber right I had to say killall -9 eclipse
>> to end the process. Now, after this episode, when ever I start eclipse it
>> hangs. It starts, pops up the gui, showing me some code I had open. It even
>> responds for a couple of seconds, but then it starts to do something and
>> eclipse stops to respond. Once again it doesn't use any cpu so it's not
>> really doing anything, but rather deadlocking or something. Now if I start
>> eclipse with the cmd trigger -data /some/other/workspace it pops up just
>> fine and wont hang.
>>
>> Now my question is what to do? I found some help on how to get things
>> working again:
>> http://wiki.eclipse.org/FAQ_How_can_I_repair_a_workspace_tha t_is_broken%3F
>> It suggests that I should file a bug report. Now if I file that above
>> mentioned story as a bug report I doubt it'll have any effect. I doubt
>> anybody can reproduce anything with it. If I'd have some logs, dumbs, etc.
>> that might help a bit... anybody has any hints on how to turn this into a
>> identifiable, possibly reproducable and most importantly fixable bug
>> report? Oh and one more thing: which category? Platform? JDT?
>>
>
> I don't have the link offhand, but there is a page somewhere on eclipse.org
> that talks about how to debug Eclipse hang
http://wiki.eclipse.org/index.php/How_to_report_a_deadlock

Dani
> s - basically, how to get a thread
> dump that will let the Eclipse devs know what is waiting for what. There is
> also an article on branching and merging with CVS in Eclipse - again, I
> don't have the link handy, don't remember if it was in Help or if it's in
> Eclipse Corner.
>
> It will help if you specify what version control system you're using (CVS?
> SVN? Perforce?), what version of Eclipse, what operating system, what
> JRE... you might want to take a look at
> http://catb.org/~esr/faqs/smart-questions.html for tips on what information
> would be helpful in reporting the bug. Some other things you might want to
> try are looking in the Eclipse error log to see if anything useful is
> getting reported there, and running eclipse -clean and/or eclipse -debug to
> see if those help.
>
> Personally, since it works with other workspaces, my suggestion would be to
> just delete and re-create that workspace (re-import the projects).
>
>
>

Report message to a moderator

Re: Merge failed -> eclipse stops responding -> killall eclipse -> broken workspace -> w [message #487017 is a reply to message #486924]

Mon, 21 September 2009 13:41

Eric Rizzo

Messages: 3070
Registered: July 2009

Senior Member

On 9/21/09 12:52 AM, Walter Harley wrote:
> "Timo"<sipulimaili@yahoo.co.uk> wrote in message
> news:h95i9v$h6m$1@build.eclipse.org...
>> I treid to merge a branch to a trunk (or more like tried to figure out how
>> to do it). This somehow failed and eclipse stopped responding. If I remeber
>> right it was trying to resolve the path and/or revision or something and
>> nothing seemed to happen. I pressed cancel, but as usual it had no effecet
>> (I don't remeber ever pressing cancel so that it would have actually
>> cancelled something, it always continues to deadlock). As cpu usage was
>> near to 0, it was clear that eclipse wasn't really doing anything. So I was
>> forced to kill eclipse. If I remeber right I had to say killall -9 eclipse
>> to end the process. Now, after this episode, when ever I start eclipse it
>> hangs. It starts, pops up the gui, showing me some code I had open. It even
>> responds for a couple of seconds, but then it starts to do something and
>> eclipse stops to respond. Once again it doesn't use any cpu so it's not
>> really doing anything, but rather deadlocking or something. Now if I start
>> eclipse with the cmd trigger -data /some/other/workspace it pops up just
>> fine and wont hang.
>>
>> Now my question is what to do? I found some help on how to get things
>> working again:
>> http://wiki.eclipse.org/FAQ_How_can_I_repair_a_workspace_tha t_is_broken%3F
>> It suggests that I should file a bug report. Now if I file that above
>> mentioned story as a bug report I doubt it'll have any effect. I doubt
>> anybody can reproduce anything with it. If I'd have some logs, dumbs, etc.
>> that might help a bit... anybody has any hints on how to turn this into a
>> identifiable, possibly reproducable and most importantly fixable bug
>> report? Oh and one more thing: which category? Platform? JDT?
>
> I don't have the link offhand, but there is a page somewhere on eclipse.org
> that talks about how to debug Eclipse hangs - basically, how to get a thread
> dump that will let the Eclipse devs know what is waiting for what. There is
> also an article on branching and merging with CVS in Eclipse - again, I
> don't have the link handy, don't remember if it was in Help or if it's in
> Eclipse Corner.
>
> It will help if you specify what version control system you're using (CVS?
> SVN? Perforce?), what version of Eclipse, what operating system, what
> JRE... you might want to take a look at
> http://catb.org/~esr/faqs/smart-questions.html for tips on what information
> would be helpful in reporting the bug. Some other things you might want to
> try are looking in the Eclipse error log to see if anything useful is
> getting reported there, and running eclipse -clean and/or eclipse -debug to
> see if those help.
>
> Personally, since it works with other workspaces, my suggestion would be to
> just delete and re-create that workspace (re-import the projects).

It is probably possible to ZIP-up and attach a non-working workspace to
a bug report. The contents of that workspace might prevent you from
doing so (eg, proprietary code that can't be shared), but if you can it
might help debug the problem.

Eric

Report message to a moderator