<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>We store transports in realtime.<br>
      Outsourcing the transport to .conf should be possible to test.<br>
      I can't tell how reproducible this issue is since it depends on
      load factors.<br>
      It has to be mentioned that some heavy webrtc load days everything
      was fine but we got the Error "Unknown Error (PJ_EUNKNOWN)" on its
      maximum load peeks.<br>
      This error also occurred just before it started to freeze some
      other day.<br>
    </p>
    <div class="moz-cite-prefix">On 2/5/21 4:08 PM, Joshua C. Colp
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAM0A2Z1BR2jHCFEbspf9rT0CzwUUfO676MxPEdRFyN9EyKXF2w@mail.gmail.com">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div dir="ltr">On Fri, Feb 5, 2021 at 11:05 AM Silvan Nagl <<a
            href="mailto:mail@53c70r.de" moz-do-not-send="true">mail@53c70r.de</a>>
          wrote:<br>
        </div>
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <div>
              <p> </p>
              <div style="font-family:-moz-fixed;font-size:12px"
                lang="x-unicode">
                <pre>Hi,

on larger webrtc setup we noticed that Asterisk 16.13.0 will start to
(deadlock)?
Asterisk keeps running without crashing but will not response to any new
connections.
Full logs attached.

It seams like 91 threads are in state "__lll_lock_wait" the mutex of
these point to thread 80 which does the webrtc stuff.
For some reason thread 80 gets a "get_write_timeout" which now starts to
destroy the transports while the other 91 threads still have a lock on
thread 80. Thread 80 has no other mutex locks.

The strace does not belong to the core dump.

We will test against 16.16 soon.
</pre>
              </div>
            </div>
          </blockquote>
          <div><br>
          </div>
          <div>Are you storing transports in realtime? If so and you
            switch to using .conf file, does the issue resolve itself?</div>
        </div>
        <div><br>
        </div>
        -- <br>
        <div dir="ltr" class="gmail_signature">
          <div dir="ltr">
            <div>
              <div dir="ltr">
                <div>
                  <div dir="ltr">
                    <div dir="ltr">
                      <div dir="ltr">
                        <div dir="ltr">
                          <div style="font-family:tahoma,sans-serif">
                            <div><font color="#073763">Joshua C. Colp</font></div>
                            <div><font color="#073763">Asterisk
                                Technical Lead</font></div>
                            <div><font color="#073763">Sangoma
                                Technologies</font></div>
                            <div><font color="#073763">Check us out at <a
                                  href="http://www.sangoma.com/"
                                  target="_blank" moz-do-not-send="true">www.sangoma.com</a> and <a
                                  href="http://www.asterisk.org/"
                                  target="_blank" moz-do-not-send="true">www.asterisk.org</a></font></div>
                          </div>
                        </div>
                      </div>
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </div>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
    </blockquote>
  </body>
</html>