'Re: dbus_connection_send_with_reply_and_block eats 100% CPU then eventually times out'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freedesktop-dbus
Subject:    Re: dbus_connection_send_with_reply_and_block eats 100% CPU then eventually times out
From:       Ralf Habacker <ralf () habacker ! de>
Date:       2015-01-31 15:10:55
Message-ID: 54CCF07F.5060902 () habacker ! de
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

Am 31.01.2015 um 14:49 schrieb Ralf Habacker:
>  
>> 5 19:27, "Ralf Habacker" <ralf@habacker.de <mailto:ralf@habacker.de>>
>> wrote:
>>
>>
>>     Am 31.01.2015 um 05:04 schrieb Alex Brooks:
>>     > Hi,
>>     >
>>     > I've been fighting for a long time with what now looks like a
>>     libdbus
>>     > bug.
>>     > I have a cut-down test program which calls a dbus method of
>>     > wpa_supplicant at 100Hz, it does this happily for several hours
>>     then
>>     > at some point the behaviour changes: any future calls sit at
>>     100% CPU
>>     > for 25sec then time out.
>>
After running about 54 minutes I got:

 counts      time (ms)
300272 3245606 signalInfo rssi=-63
300273 3245616 signalInfo rssi=-63
Error: wpa_supplicant DBus error in signalPoll: Did not receive a reply.
Possible causes include: the remote application did not send a reply,
the message bus security policy blocked the reply, the reply timeout
expired, or the network connection was broken.

Ralf

[Attachment #5 (text/html)]

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <br>
    <div class="moz-cite-prefix">Am 31.01.2015 um 14:49 schrieb Ralf
      Habacker:<br>
    </div>
    <blockquote cite="mid:54CCDD4E.9060505@habacker.de" type="cite">
      <meta content="text/html; charset=windows-1252"
        http-equiv="Content-Type">

      <blockquote
cite="mid:CAE8XxP-w5Fjbfd_ENdNh2sY=AOkgbnNfSuJF1N0ACVq+8mf2YA@mail.gmail.com"
        type="cite">
        <div class="gmail_quote">5 19:27, "Ralf Habacker" &lt;<a
            moz-do-not-send="true" href="mailto:ralf@habacker.de">ralf@habacker.de</a>&gt;

          wrote:<br type="attribution">
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
            Am 31.01.2015 um 05:04 schrieb Alex Brooks:<br>
            &gt; Hi,<br>
            &gt;<br>
            &gt; I've been fighting for a long time with what now looks
            like a libdbus<br>
            &gt; bug.<br>
            &gt; I have a cut-down test program which calls a dbus
            method of<br>
            &gt; wpa_supplicant at 100Hz, it does this happily for
            several hours then<br>
            &gt; at some point the behaviour changes: any future calls
            sit at 100% CPU<br>
            &gt; for 25sec then time out.<br>
          </blockquote>
        </div>
      </blockquote>
    </blockquote>
    After running about 54 minutes I got: <br>
    <br>
     counts      time (ms) <br>
    300272 3245606 signalInfo rssi=-63<br>
    300273 3245616 signalInfo rssi=-63<br>
    Error: wpa_supplicant DBus error in signalPoll: Did not receive a
    reply. Possible causes include: the remote application did not send
    a reply, the message bus security policy blocked the reply, the
    reply timeout expired, or the network connection was broken.<br>
    <br>
    Ralf <br>
  </body>
</html>

[Attachment #6 (text/plain)]

_______________________________________________
dbus mailing list
dbus@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dbus

[prev in list] [next in list] [prev in thread] [next in thread] 