Anyone running tmux and observing weird CPU usage?

Is anyone here running tmux and observing what looks like an ever-increasing CPU usage under the Linode graphs?

I run a constant tmux session, which is basically only used for irssi. Every week day, I re-attach to my tmux session around 8AM. That's when the CPU usage slowly starts to build. I disconnect at around 3PM and my CPU usage drops back down to zero. I observe that behaviour every day.

Here's what my monthly CPU usage looks like :

~~![](<URL url=)http://imgur.com/s98xS.png" />

(I don't have a daily graph to better illustrate this, I went back to screen for the moment.)

I started keeping an eye on my CPU usage using htop. I don't see a constant CPU usage; just a peak ever 30 seconds or so.

This is tmux 1.3 on Ubuntu 10.10 x86. I was previously running Debian testing x86, same tmux version. I was observing the same behaviour.

I'm just curious to know if I'm the only one seeing this. I checked tmux's bugtracker and the mailing list but I don't see anything close to this. Some people have reported constant CPU usage @ 100% in version 1.2, but nothing close to what I am experiencing.

I also tried the CVS HEAD version of tmux last night, same behaviour.

Thanks!~~

9 Replies

I am running into the very same issue with tmux on 10.04 from apt. Have you gotten anywhere with this issue?

Sadly, no. I tried the lastest CVS HEAD version, and also tried moving from Debian -testing to Ubuntu 10.10 and the behaviour still occurs.

Kinda gave up at the moment and went back to screen because the pacakge in Ubuntu/Debian has the vertical split patch included.

I know it's been a long time since this problem were reported here but I'm experiencing the same behavior.

I'm using tmux 1.3-2+squeeze1 under Debian 6.0.3.

~~![](<URL url=)http://ompldr.org/vYnBmYg/fuck_the_tmux.jpg" />

At some time between 22h and 0h I detached the session and around 9 I reattached to it.

Have you guys solved your problem some way?

Thanks!~~

I moved back from Ubuntu to Debian Testing some time ago, and the problem has disappeared.

Running tmux 1.5-3 on a Debian Testing node using the latest Latest 3.0 kernel.

Are you using the 3.x series kernel, or a 2.6 kernel?

@Kint:

I moved back from Ubuntu to Debian Testing some time ago, and the problem has disappeared.

Running tmux 1.5-3 on a Debian Testing node using the latest Latest 3.0 kernel.

Are you using the 3.x series kernel, or a 2.6 kernel?

I'm running debian stable, so i'm on a 2.6 kernel and with an older tmux. Will try to get the newer one and test with it before upgrading the whole system (which I'll try to avoid).

Thanks for your answer!

If you want to stick with Squeeze, try grabbing the latest tmux sources and making a simple Debian package with CheckInstall.

https://help.ubuntu.com/community/CheckInstall

I think tmux 1.5 solved it for me.

@Kint:

If you want to stick with Squeeze, try grabbing the latest tmux sources and making a simple Debian package with CheckInstall.

https://help.ubuntu.com/community/CheckInstall

I think tmux 1.5 solved it for me.

Thanks a lot for the CheckInstall suggestion, wasn't aware of it and it's really nice.

Upgrading to tmux 1.5 solved the problem.

Thanks again!

@marc0s:

I'm running debian stable, so i'm on a 2.6 kernel and with an older tmux.

It's better to use Squeeze-Backports (less troubles when upgrading). I.E.:

http://packages.debian.org/squeeze-backports/tmux

Besides, you can run 3.x kernel with Squeeze. I'm currently running 3.0.4-linode38 with it.

@advocatux:

@marc0s:

I'm running debian stable, so i'm on a 2.6 kernel and with an older tmux.

It's better to use Squeeze-Backports (less troubles when upgrading). I.E.:

http://packages.debian.org/squeeze-backports/tmux

I totally forgot about backports… Didn't either mind to check if tmux was available there… Probably it's a better idea as you say regarding upgrades.

Thanks

Reply

Please enter an answer
Tips:

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct