<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [bug] rapidly switching VTs between Weston and a Terminal can lock Weston"
href="https://bugs.freedesktop.org/show_bug.cgi?id=69764#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [bug] rapidly switching VTs between Weston and a Terminal can lock Weston"
href="https://bugs.freedesktop.org/show_bug.cgi?id=69764">bug 69764</a>
from <span class="vcard"><a class="email" href="mailto:rafal.mielniczuk2@gmail.com" title="Rafal Mielniczuk <rafal.mielniczuk2@gmail.com>"> <span class="fn">Rafal Mielniczuk</span></a>
</span></b>
<pre>I am not 100% sure if this is related, but in drm backend, after switching vt a
couple of times, open fds get accumulated by the weston-launch process. When
their count hits system limits, it then hangs the weston session.
Errors show:
Error opening device /dev/input/event6: Too many open files
Open fds after some vt switches:
$ sudo ls -l /proc/14112/fd
lrwx------ 1 root root 64 10-17 21:19 0 -> /dev/tty1
lrwx------ 1 root root 64 10-17 21:19 1 -> /dev/tty1
lrwx------ 1 root root 64 10-17 21:19 10 -> /dev/input/event5
lrwx------ 1 root root 64 10-17 21:19 11 -> /dev/input/event13
lrwx------ 1 root root 64 10-17 21:19 12 -> /dev/input/event7
lrwx------ 1 root root 64 10-17 21:19 13 -> /dev/input/event10
lrwx------ 1 root root 64 10-17 21:19 14 -> /dev/input/event8
lrwx------ 1 root root 64 10-17 21:19 15 -> /dev/input/event9
lrwx------ 1 root root 64 10-17 21:19 16 -> /dev/input/event2
lrwx------ 1 root root 64 10-17 21:19 17 -> /dev/input/event12
lrwx------ 1 root root 64 10-17 21:19 18 -> /dev/input/event6
lrwx------ 1 root root 64 10-17 21:19 19 -> /dev/input/event11
lrwx------ 1 root root 64 10-17 21:19 2 -> /dev/tty1
lrwx------ 1 root root 64 10-17 21:19 20 -> /dev/input/event1
lrwx------ 1 root root 64 10-17 21:19 21 -> /dev/input/event4
lrwx------ 1 root root 64 10-17 21:19 22 -> /dev/input/event3
lrwx------ 1 root root 64 10-17 21:19 23 -> /dev/input/event0
lrwx------ 1 root root 64 10-17 21:19 24 -> /dev/input/event5
lrwx------ 1 root root 64 10-17 21:19 25 -> /dev/input/event13
lrwx------ 1 root root 64 10-17 21:19 26 -> /dev/input/event7
lrwx------ 1 root root 64 10-17 21:19 27 -> /dev/input/event10
lrwx------ 1 root root 64 10-17 21:19 28 -> /dev/input/event8
lrwx------ 1 root root 64 10-17 21:19 29 -> /dev/input/event9
lrwx------ 1 root root 64 10-17 21:19 3 -> socket:[81634]
lrwx------ 1 root root 64 10-17 21:19 30 -> /dev/input/event2
lrwx------ 1 root root 64 10-17 21:19 31 -> /dev/input/event12
lrwx------ 1 root root 64 10-17 21:19 32 -> /dev/input/event6
lrwx------ 1 root root 64 10-17 21:19 33 -> /dev/input/event11
lrwx------ 1 root root 64 10-17 21:19 4 -> /dev/dri/card0
lrwx------ 1 root root 64 10-17 21:19 5 -> anon_inode:[signalfd]
lrwx------ 1 root root 64 10-17 21:19 6 -> /dev/input/event1
lrwx------ 1 root root 64 10-17 21:19 7 -> /dev/input/event4
lrwx------ 1 root root 64 10-17 21:19 8 -> /dev/input/event3
lrwx------ 1 root root 64 10-17 21:19 9 -> /dev/input/event0</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>