Description of problem: I used tmux as byobu backend. Two things were running in tmux when it crashed: * bash and journalctl -f * bash and btrfs scrub in foreground of a backup drive * several other bashes were idling The scrub kept running in background for some time and finished without an error. Version-Release number of selected component: tmux-1.9a-2.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: tmux -2 -f /usr/share/byobu/profiles/tmuxrc new-session -n - /usr/bin/byobu-shell crash_function: __tsearch executable: /usr/bin/tmux kernel: 3.14.3-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #6 __tsearch at tsearch.c:280 #7 __add_to_environ at setenv.c:212 #8 __setenv at setenv.c:307 #9 environ_push at environ.c:176 #10 job_run at job.c:66 #11 status_find_job at status.c:535 #12 status_replace1 at status.c:386 #13 status_replace at status.c:470 #14 status_redraw_get_right at status.c:108 #15 status_redraw at status.c:183
Created attachment 896671 [details] File: backtrace
Created attachment 896672 [details] File: cgroup
Created attachment 896673 [details] File: core_backtrace
Created attachment 896674 [details] File: dso_list
Created attachment 896675 [details] File: environ
Created attachment 896676 [details] File: exploitable
Created attachment 896677 [details] File: limits
Created attachment 896678 [details] File: maps
Created attachment 896679 [details] File: open_fds
Created attachment 896680 [details] File: proc_pid_status
Created attachment 896681 [details] File: var_log_messages
Hi Florian, are you able to reproduce the issue (ex, following a test case)? I'm asking it because I need a way to reproduce the issue, before report it to upstream, otherwise they'll close the bug.
Hi Filipe, thank you for your answer! I fear I wasn't able to reproduce it, so I think it's better to close it for now and maybe reopen if somebody can.