Killing buffer fails, pegs CPU, eats memory

oscarfv commented 11 years ago

Start emacs -Q and eval this code in scratch :

(ido-mode)
(setq ido-enable-flex-matching t)
(require 'flx-ido)
(flx-ido-mode 1)

(get-buffer-create "foo-1")
(get-buffer-create "foo-2")
(get-buffer-create "foo-3")

Now press C-x b for switching buffers.
Type foo and the list is reduced to the foo-buffers.
Press C-k for killing the buffer at the front of the list. The list remains the same (although the buffer was killed.)
Press C-s several times for cycling the list. When the "killed" buffer comes again to the front of the list, Emacs is using 100% CPU and eating memory at a fast pace.
C-g returns control to the user.

lewang commented 11 years ago

Thanks for the detailed repro, will look at this soon.

aspiers commented 10 years ago

I can also reproduce this.

lewang commented 10 years ago

Thanks. I will look at this bug first. Since I don't use ido myself, I didn't know C-k was available.

On Sat, Dec 14, 2013 at 5:56 PM, Adam Spiers notifications@github.comwrote:

I can also reproduce this.

— Reply to this email directly or view it on GitHubhttps://github.com/lewang/flx/issues/46#issuecomment-30593391 .

Le

oscarfv commented 10 years ago

After a quick test the fix seems to work.

This bug was a nasty one. Thanks for fixing it.

lewang / flx

Killing buffer fails, pegs CPU, eats memory #46