Restarting i3 in-place twice segfaults the i3 process.

Output of i3 --moreversion 2>&- || i3 --version:

Binary i3 version: 4.12 (2016-03-06, branch "4.12") © 2009 Michael Stapelberg and contributors Running i3 version: 4.12 (2016-03-06, branch "4.12") (pid 10360) Loaded i3 config: /home/pjr/.i3/config (Last modified: Sat 30 Jul 2016 12:57:41 BST, 119555 seconds ago)

The i3 binary you just called: /usr/bin/i3 The i3 binary you are running: i3

URL to a logfile as per http://i3wm.org/docs/debugging.html:

http://logs.i3wm.org/logs/5691420614590464.bz2

(This log probably won't be very useful, as it's from the i3 session I started after the crash in order to file this report...)

What I did:

Hit $mod+Shift-R twice. It doesn't seem to matter how much time elapses in between.

(Edited to add: Since opening this issue I've discovered that it only seems to happen when I have a second monitor plugged in.)

What I saw:

i3 crashed and dumped me back to the login screen; I also found the following line in my syslog:

i3[9844]: segfault at 0 ip 000055be987cef96 sp 00007ffe74a3ed50 error 6 in i3[55be987ac000+68000]

No dialog appeared offering the option to save a backtrace.

What I expected instead:

i3 to restart in-place.