Discussion:
tmux server crashes
Il Memming Park
2014-10-25 19:19:59 UTC
Permalink
Hi all,

I'm using tmux 1.9a on Mac OS (13.4.0), homebrew version. I use it with ViM
REPL environment called slimux (https://github.com/epeli/slimux). As far as
I understand it sends selected text via calling 'tmux set-buffer' and 'tmux
paste-buffer -t'.
It works great, but after some extensive buffer copy & paste operations,
tmux can't take it anymore, and just crashes taking all children with it.
The amount of text that goes through the buffer is generally less than 1kb.
Is this a known issue and is there a solution?

Memming
--
Memming Park
http://www.memming.com | ***@twitter
Nicholas Marriott
2014-10-30 08:18:48 UTC
Permalink
Do you have a backtrace?
Post by Il Memming Park
Hi all,
I'm using tmux 1.9a on Mac OS (13.4.0), homebrew version. I use it with
ViM REPL environment called slimux ([1]https://github.com/epeli/slimux).
As far as I understand it sends selected text via calling 'tmux
set-buffer' and 'tmux paste-buffer -t'.
It works great, but after some extensive buffer copy & paste operations,
tmux can't take it anymore, and just crashes taking all children with it.
The amount of text that goes through the buffer is generally less than
1kb. Is this a known issue and is there a solution?
Memming
--
Memming Park
References
Visible links
1. https://github.com/epeli/slimux
2. http://www.memming.com/
------------------------------------------------------------------------------
_______________________________________________
tmux-users mailing list
https://lists.sourceforge.net/lists/listinfo/tmux-users
------------------------------------------------------------------------------
Nicholas Marriott
2014-10-30 10:34:48 UTC
Permalink
Make sure you have a tmux built with debug symbols (configure with
--enable-debug), then best bet is to do this:

$ pkill tmux
$ tmux new -d
$ gdb -q tmux `pgrep tmux`
(gdb) c

Then do "tmux a" from another window and reproduce. When it crashes, go
back to the gdb window and do "bt full" and show me the output.
No. It didn't leave a dump. How would I obtain one? Fire up gdb?
Thanks.
Memming
On Oct 30, 2014 3:19 AM, "Nicholas Marriott"
Do you have a backtrace?
* * Hi all,
* * I'm using tmux 1.9a on Mac OS (13.4.0), homebrew version. I use it
with
* * ViM REPL environment called slimux
([1][2]https://github.com/epeli/slimux).
* * As far as I understand it sends selected text via calling 'tmux
* * set-buffer' and 'tmux paste-buffer -t'.
* * It works great, but after some extensive buffer copy & paste
operations,
* * tmux can't take it anymore, and just crashes taking all children
with it.
* * The amount of text that goes through the buffer is generally less
than
* * 1kb. Is this a known issue and is there a solution?
* * Memming
* * --
* * Memming Park
References
* * Visible links
* * 1. [4]https://github.com/epeli/slimux
* * 2. [5]http://www.memming.com/
------------------------------------------------------------------------------
_______________________________________________
tmux-users mailing list
[7]https://lists.sourceforge.net/lists/listinfo/tmux-users
References
Visible links
2. https://github.com/epeli/slimux
3. http://www.memming.com/
4. https://github.com/epeli/slimux
5. http://www.memming.com/
7. https://lists.sourceforge.net/lists/listinfo/tmux-users
------------------------------------------------------------------------------
Il Memming Park
2014-10-30 16:48:13 UTC
Permalink
Thank you for the kind instructions. I'll report back soon.

Memming
Post by Nicholas Marriott
Make sure you have a tmux built with debug symbols (configure with
$ pkill tmux
$ tmux new -d
$ gdb -q tmux `pgrep tmux`
(gdb) c
Then do "tmux a" from another window and reproduce. When it crashes, go
back to the gdb window and do "bt full" and show me the output.
No. It didn't leave a dump. How would I obtain one? Fire up gdb?
Thanks.
Memming
On Oct 30, 2014 3:19 AM, "Nicholas Marriott"
Do you have a backtrace?
* * Hi all,
* * I'm using tmux 1.9a on Mac OS (13.4.0), homebrew version. I
use it
with
* * ViM REPL environment called slimux
([1][2]https://github.com/epeli/slimux).
* * As far as I understand it sends selected text via calling 'tmux
* * set-buffer' and 'tmux paste-buffer -t'.
* * It works great, but after some extensive buffer copy & paste
operations,
* * tmux can't take it anymore, and just crashes taking all
children
with it.
* * The amount of text that goes through the buffer is generally
less
than
* * 1kb. Is this a known issue and is there a solution?
* * Memming
* * --
* * Memming Park
References
* * Visible links
* * 1. [4]https://github.com/epeli/slimux
* * 2. [5]http://www.memming.com/
------------------------------------------------------------------------------
_______________________________________________
tmux-users mailing list
[7]https://lists.sourceforge.net/lists/listinfo/tmux-users
References
Visible links
2. https://github.com/epeli/slimux
3. http://www.memming.com/
4. https://github.com/epeli/slimux
5. http://www.memming.com/
7. https://lists.sourceforge.net/lists/listinfo/tmux-users
Il Memming Park
2014-11-26 23:09:53 UTC
Permalink
I've been running debug enabled tmux 2.0 for weeks and it hasn't crashed so
far. Perhaps it was a bug in tmux 1.9.
Post by Il Memming Park
Thank you for the kind instructions. I'll report back soon.
Memming
Post by Nicholas Marriott
Make sure you have a tmux built with debug symbols (configure with
$ pkill tmux
$ tmux new -d
$ gdb -q tmux `pgrep tmux`
(gdb) c
Then do "tmux a" from another window and reproduce. When it crashes, go
back to the gdb window and do "bt full" and show me the output.
No. It didn't leave a dump. How would I obtain one? Fire up gdb?
Thanks.
Memming
On Oct 30, 2014 3:19 AM, "Nicholas Marriott"
Do you have a backtrace?
* * Hi all,
* * I'm using tmux 1.9a on Mac OS (13.4.0), homebrew version. I
use it
with
* * ViM REPL environment called slimux
([1][2]https://github.com/epeli/slimux).
* * As far as I understand it sends selected text via calling
'tmux
* * set-buffer' and 'tmux paste-buffer -t'.
* * It works great, but after some extensive buffer copy & paste
operations,
* * tmux can't take it anymore, and just crashes taking all
children
with it.
* * The amount of text that goes through the buffer is generally
less
than
* * 1kb. Is this a known issue and is there a solution?
* * Memming
* * --
* * Memming Park
References
* * Visible links
* * 1. [4]https://github.com/epeli/slimux
* * 2. [5]http://www.memming.com/
------------------------------------------------------------------------------
_______________________________________________
tmux-users mailing list
[7]https://lists.sourceforge.net/lists/listinfo/tmux-users
References
Visible links
2. https://github.com/epeli/slimux
3. http://www.memming.com/
4. https://github.com/epeli/slimux
5. http://www.memming.com/
7. https://lists.sourceforge.net/lists/listinfo/tmux-users
--
IL Memming Park
Postdoc | University of Texas at Austin
http://www.memming.com | ***@Twitter
Loading...