Re: Vim freezes with 100% cpu usage on exit

Hi Christian

I don't think the bug is specific to ubuntu, I'm guessing that the problem is that x11 client libraries weren't designed for applications that survive across multiple x11 sessions which is what happens when running terminal apps that connect to x11.

Thanks for the '-X' flags by the way, I'd rather keep vim compiled with gtk on my system

On Sat, Apr 20, 2013 at 11:33 AM, Christian Brabandt <cblists@256bit.org> wrote:

Hi Thiago!

On Sa, 20 Apr 2013, Thiago Padilha wrote:

> Dominique thanks for your help.
>
> I have attached gdb to vim in both cases: when I re-attach to tmux after a
> reboot(which hangs without cpu activity for a while) and soon after that,
> when I send the quit command(which hangs vim with 100% cpu).
>
> In both cases it seems the issue is related with x11 libraries and the fact
> that my x11 session(provided by cygwin-x) has a different lifecycle than
> the vim session. The function that causes vim to freeze with 100% cpu is
> '_XtWaitForSomething' from libXt. As the name says this function waits for
> something that never happens with a busy poll which causes the freeze.
>
> The issue was fixed for me by replacing ubuntu's 'vim-gtk' for 'vim-nox'
> package. The x11 clipboard integration I replaced by creating mappings that
> invoke the xclip commandline utility(which doesn't keep a connection with
> x11 open).
>
> In any case I attached gdb backtraces for anyone interested in doing
> further investigations. It may be possible to reproduce these issues by
> starting vim with x11 support in a tmux/screen session, restarting x11 and
> then reattaching to it. To debug in debian/ubuntu just install the
> vim-gtk/vim-dbg packages

> backtrace after tmux attach(triggered by clicking at the vim pane with
> the mouse, but this will call eventually returns):

Hm, Your backtrace looks like the one I just got for a similar problem.
Look for the subject hanging vim, I just posted there yesterday. Maybe
this is a problem with the Ubuntu X11 libraries?

In any case, starting vim with -X should also fix this for you.

regards,
Christian

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
 
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.