Bug 77885 - chvt'ing really fast between 2 xservers can cause a crash because master may not be dropped
Summary: chvt'ing really fast between 2 xservers can cause a crash because master may ...
Status: RESOLVED MOVED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-24 10:19 UTC by Maarten Lankhorst
Modified: 2018-12-13 22:30 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
xserver logs showing the relevant parts of both xservers (4.92 KB, text/plain)
2014-04-24 10:19 UTC, Maarten Lankhorst
no flags Details

Description Maarten Lankhorst 2014-04-24 10:19:17 UTC
Created attachment 97891 [details]
xserver logs showing the relevant parts of both xservers

This crash happened for me when I ran 2 xservers in valgrind (to slow it down and to make races more likely) on vt 7 and 8 and did a quick change between them:

"chvt 8; chvt 7; chvt 8; chvt 7; chvt 8; chvt 7"

But for a more generic case: while chvt 7; do chvt 8; done
Comment 1 Chris Wilson 2014-04-24 11:03:38 UTC
Care to encapsulate that into a test script?

I think you used:

#/bin/sh
X -novtswitch vt7 :0 &
X -novtswitch vt8 :1 &
while chvt 7 ; do chvt 8; done
Comment 2 Maarten Lankhorst 2014-04-24 12:01:45 UTC
Hm what seems to happen with that testcase is that chvt times out. Poking it by starting a x client on both server kills one.

So the easiest testcase would be:

#!/bin/sh
Xorg -novtswitch vt7 :0 &
Xorg -novtswitch vt8 :1 &

sleep 5

DISPLAY=:0 xeyes &
p1=$!
DISPLAY=:1 xeyes &
p2=$!

(sleep 20; kill $p1 $p2) &

chvt 8; chvt 7; chvt 8; chvt 7; chvt 8; chvt 7
Comment 3 GitLab Migration User 2018-12-13 22:30:10 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/457.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.