Re: [Subclipse-users] Commit crashes Eclipse

On Wed, Oct 26, 2011 at 9:50 AM, Bryan Evenson <bevenson_at_melinkcorp.com> wrote:

> I've got Subclipse 1.8.2 up and running.  I can access the repository, have added folders to the repository, completed
> a checkout and have marked files to be added all through Subclipse.  Verification through the command line appears
> that everything seems to be okay.  I then attempt to commit the files through Subclipse.  After I add the comment and
> click OK, Eclipse exits.  When I open up Eclipse, I have the following error in the error log:

When JavaHL crashes you would need to look to see if the JVM produced
a dump. There will not be anything in the Eclipse error log.

> From inspecting things from the command line, it appears that the top level directory was locked before Eclipse crashed.
> svn:needslock is not set on anything in the repository (or on my working copy), so I'm not sure why the directory is getting
> locked.  Doing a cleanup and commit from the command line worked just fine.  I have reproduced this issue several times
> with different combinations of files (single file commits, multiple file commits spanning multiple directories, etc).  Any ideas what may be going wrong?

Subversion uses the term "lock" for a lot of things. Most likely it
is talking about a working copy lock, which SVN creates internally
whenever it is doing an operation where it needs to update the working
copy. Since you crashed during a commit it would not be a surprise
for the working copy to be locked.

svn cleanup should remove the lock.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2864297
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].