Commit command never completes and consumes 100% CPU

[Nicholas Allen]

Looking at the stack trace it seems to be the search plugin that is
causing this. After unistalling the plugin this problem went away. I'll
report a bug in bzr-search plugin....

Nick

John Arbash Meinel wrote:
> Nicholas Allen wrote:
> > Hi,
>
> > I just started experiencing a strange bug with Bazaar. I made 9
> > commits on a branch and then merged that branch to my trunk branch
> > (which is bound to a remote location using smart server). When I
> > commit the merge Bazaar prints:
>
> > [####\               ] bzr+ssh >      1KB     2KB/s |
> > Indexing...:Indexing texts:Walking content 1239/1289
>
> > At this point CPU usage shoots up to 100% and even after 20 minutes my
> > commit has not completed. None of the work I did in the branch changed
> > large numbers of files. I am using a smart server with the following
> > version info:
>
> > Bazaar (bzr) 1.14dev
> >   Python interpreter: /usr/bin/python 2.5.2
> >   Python standard library: /usr/lib/python2.5
> >   bzrlib: /usr/lib/python2.5/site-packages/bzrlib
>
> > Any help greatly appreciated!
>
> > Nick
>
> What is the version of the remote server?
>
> My initial guess is that the autopack code is being triggered. However
> with newer versions of bzr that should be happening on the server, which
> shouldn't be effecting your local machine as much.
>
> I would also mention that you can use ^| (Ctrl+|, or SIGQUIT, IIRC) to
> cause bzr to drop into a debugger. Then you can use 'bt' to print out
> the backtrace, which will tell us what bzr is currently working on. You
> can then use "c" to have it continue doing whatever it was doing.
>
> John
> =:->