qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, kraxel@redhat.com
Subject: Re: [Qemu-devel] 100% host cpu with gtk3
Date: Wed, 6 Jun 2018 12:37:52 +0100	[thread overview]
Message-ID: <20180606113752.GA3064@redhat.com> (raw)
In-Reply-To: <20180606104357.GB3205@lemon.usersys.redhat.com>

On Wed, Jun 06, 2018 at 06:43:57PM +0800, Fam Zheng wrote:
> Hi Gerd,
> 
> When using the gtk frontend, it seems there is a busy loop in libgtk repeatedly
> calling recvmsg, causing 100% cpu on the main thread. This started to appear
> after I upgraded to Fedora 28. Is this a known problem?
> 
> Any hints on how to track it down?

GLib has systemtap probes registered in its dispatch code. These probes
will include the name of the GSource. You could possibly use this to
identify which GSource is firing too often.

eg in gmain.c in glib code there are these events to hook into:

          TRACE (GLIB_MAIN_BEFORE_DISPATCH (g_source_get_name (source), source,
                                            dispatch, callback, user_data));
          need_destroy = !(* dispatch) (source, callback, user_data);
          TRACE (GLIB_MAIN_AFTER_DISPATCH (g_source_get_name (source), source,
                                           dispatch, need_destroy));



Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

      parent reply	other threads:[~2018-06-06 11:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-06 10:43 [Qemu-devel] 100% host cpu with gtk3 Fam Zheng
2018-06-06 11:37 ` Gerd Hoffmann
2018-06-06 11:37 ` Daniel P. Berrangé [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180606113752.GA3064@redhat.com \
    --to=berrange@redhat.com \
    --cc=famz@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).