tmux in uninterruptible sleep (D) state bug

Discussion:

Gonzalo Ciruelos

2015-02-23 01:32:51 UTC

Hello,
For some weeks now I'm having this bug with tmux. It happens when I run
some code (short C++ programs made by me, I think it has to do with bad
memory management or non-termination). The zsh prompt where I ran "./a.out"
completely feezes along with tmux. I can kill the terminal tmux is running
in, and open another one. Every attempt at killing tmux fails. The top
utility says tmux is in D state (uninterruptible state), and the only thing
you can do to kill a program in that state is rebooting.
Some applications running in tmux continue working (I can hear the music
that is being played by cmus, for example), but tmux does not respond to
any key combination.

This is obviously a very annoying bug. Is it known? (some googling suggests
it is not)

I'm running tmux 1.9a-1 in archlinux, with the gnome-terminal (3.14.2) and
zsh (5.0.7) as shell.

Here [1] is a piece of code (not minimal) that triggers the bug

Thank you very much.

[1] https://gist.github.com/gciruelos/0699591f5acdef8d7ad4

Nicholas Marriott

2015-02-23 08:54:44 UTC

Permalink

Your program just recurses forever until it blows up the stack. It
doesn't have any effect on tmux whatsoever here. Sounds like a bug
somewhere else in your system, I'd guess kernel.

Post by Gonzalo Ciruelos
Hello,
For some weeks now I'm having this bug with tmux. It happens when I run
some code (short C++ programs made by me, I think it has to do with bad
memory management or non-termination). The zsh prompt where I ran
"./a.out" completely feezes along with tmux. I can kill the terminal tmux
is running in, and open another one. Every attempt at killing tmux fails.
The top utility says tmux is in D state (uninterruptible state), and the
only thing you can do to kill a program in that state is rebooting.
Some applications running in tmux continue working (I can hear the music
that is being played by cmus, for example), but tmux does not respond to
any key combination.
This is obviously a very annoying bug. Is it known? (some googling
suggests it is not)
I'm running tmux 1.9a-1 in archlinux, with the gnome-terminal (3.14.2) and
zsh (5.0.7) as shell.
Here [1] is a piece of code (not minimal) that triggers the bug**
Thank you very much.
[1] **[1]https://gist.github.com/gciruelos/0699591f5acdef8d7ad4
References
Visible links
1. https://gist.github.com/gciruelos/0699591f5acdef8d7ad4
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
_______________________________________________
tmux-users mailing list
https://lists.sourceforge.net/lists/listinfo/tmux-users

Nicholas Marriott

2015-02-23 09:03:32 UTC

Permalink

Does it go away if you run "ulimit -c0" before running your program?

Post by Nicholas Marriott
Your program just recurses forever until it blows up the stack. It
doesn't have any effect on tmux whatsoever here. Sounds like a bug
somewhere else in your system, I'd guess kernel.