<html>
    <head>
      <base href="https://bugs.freedesktop.org/" />
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Priority</th>
          <td>medium
          </td>
        </tr>

        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW --- - weston-terminal: exits under intensive terminal output"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=83297">83297</a>
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>wayland-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>weston-terminal: exits under intensive terminal output
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>normal
          </td>
        </tr>

        <tr>
          <th>Classification</th>
          <td>Unclassified
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>Linux (All)
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>courmisch@gmail.com
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>x86-64 (AMD64)
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>1.5.0
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>weston
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>Wayland
          </td>
        </tr></table>
      <p>
        <div>
        <pre>While the virtual terminal underneath weston-terminal wants to output a lot of
data really fast, the terminal process may pseudo-randomly exit abruptly.

When this happens, the Weston error console will show something like:

| Error sending request: Resource temporarily unavailable
| child 7795 exited

On my system, this happens about one in two/tree times running "ls -lR /", but
I initially observed the problem with "vlc -vv".

Given the error message, I assume that the Wayland display socket has its
kernel-level buffers saturated in the client-to-server direction, and
libwayland-client exits instead of gracefully handling the transient error due
to non-blocking mode. This is however merely a conjecture.


This bug was originally reported as Debian #760043.</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>