XOrg crashing randomly

[lheckemann]

Issue description

What the title says: this typically happens about once a day. Appears to be distinct from #21026 based on the stack trace:

#0  0x00007faa7867d0f3 in __GI__IO_default_xsputn () from /nix/store/7crrmih8c52r8fbnqb933dxrsp44md93-glibc-2.25/lib/libc.so.6
#1  0x00007faa78670c6d in __GI__IO_padn () from /nix/store/7crrmih8c52r8fbnqb933dxrsp44md93-glibc-2.25/lib/libc.so.6
#2  0x00007faa786504d0 in vfprintf () from /nix/store/7crrmih8c52r8fbnqb933dxrsp44md93-glibc-2.25/lib/libc.so.6
#3  0x00007faa786fe7c6 in __vsnprintf_chk () from /nix/store/7crrmih8c52r8fbnqb933dxrsp44md93-glibc-2.25/lib/libc.so.6
#4  0x00007faa786fe728 in __snprintf_chk () from /nix/store/7crrmih8c52r8fbnqb933dxrsp44md93-glibc-2.25/lib/libc.so.6
#5  0x00007faa781dcb27 in pci_device_vgaarb_set_target () from /nix/store/ix3l6ys32kxjlljg64nkyc03az337sp9-libpciaccess-0.13.4/lib/libpciaccess.so.0
#6  0x000000000049273c in VGAarbiterSpriteMoveCursor ()
#7  0x0000000000492753 in VGAarbiterSpriteMoveCursor ()
#8  0x0000000000492753 in VGAarbiterSpriteMoveCursor ()
#9  0x0000000000492753 in VGAarbiterSpriteMoveCursor ()
#10 0x0000000000492753 in VGAarbiterSpriteMoveCursor ()
#11 0x0000000000492753 in VGAarbiterSpriteMoveCursor ()
#12 0x0000000000492753 in VGAarbiterSpriteMoveCursor ()
#13 0x0000000000492753 in VGAarbiterSpriteMoveCursor ()
#14 0x0000000000492753 in VGAarbiterSpriteMoveCursor ()
#15 0x0000000000492753 in VGAarbiterSpriteMoveCursor ()
#16 0x0000000000492753 in VGAarbiterSpriteMoveCursor ()
#17 0x0000000000492753 in VGAarbiterSpriteMoveCursor ()
#18 0x0000000000492753 in VGAarbiterSpriteMoveCursor ()
#19 0x0000000000492753 in VGAarbiterSpriteMoveCursor ()
#20 0x0000000000492753 in VGAarbiterSpriteMoveCursor ()
#21 0x0000000000492753 in VGAarbiterSpriteMoveCursor ()
#22 0x0000000000492753 in VGAarbiterSpriteMoveCursor ()
#23 0x0000000000492753 in VGAarbiterSpriteMoveCursor ()
#24 0x0000000000492753 in VGAarbiterSpriteMoveCursor ()
#25 0x0000000000492753 in VGAarbiterSpriteMoveCursor ()

(and so on for many more frames, so I'm guessing it's a stack corruption bug?). I have a core dump but I'm not posting it because I'm not sure if it might contain sensitive information — if anyone can advise me concerning that it would be much appreciated!

Steps to reproduce

Unknown.

Technical details

• System: 17.03.1052.aa0383397a (Gorilla)
• Nix version: nix-env (Nix) 1.11.8
• Nixpkgs version: "17.03.1052.aa0383397a"

[vcunat]

We can try this update: https://lists.x.org/archives/xorg-announce/2017-April/002791.html – perhaps this point will help:

vgaarb: add a the trailing NULL character on read(vgaarb_fd)

[lheckemann]

I haven't encountered this any more, and nobody else has confirmed this, so I'll close it.