dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 28069] maniadrive - smooth play with LIBGL_ALWAYS_INDIRECT=true, (almost) unplayable otherwise
Date: Fri, 14 May 2010 07:32:00 -0700 (PDT)	[thread overview]
Message-ID: <20100514143200.2ED5913004E@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-28069-502@http.bugs.freedesktop.org/>

https://bugs.freedesktop.org/show_bug.cgi?id=28069

--- Comment #5 from Michel Dänzer <michel@daenzer.net> 2010-05-14 07:31:59 PDT ---
Quite a few more extensions are available with direct rendering, e.g.
GLX_SGI_video_sync. Maybe there's a problem with one of those. Might be
interesting to, with direct rendering:

* If the maniadrive process hogs the CPU: Get a profile with sysprof or
oprofile.
* Otherwise: Interrupt execution at regular intervals in gdb and see if it's in
a particular place most of the time.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2010-05-14 14:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-11 19:46 [Bug 28069] New: maniadrive - smooth play with LIBGL_ALWAYS_INDIRECT=true, (almost) unplayable otherwise bugzilla-daemon
2010-05-12 11:50 ` [Bug 28069] " bugzilla-daemon
2010-05-12 20:15 ` bugzilla-daemon
2010-05-12 20:16 ` bugzilla-daemon
2010-05-12 20:16 ` bugzilla-daemon
2010-05-14 14:32 ` bugzilla-daemon [this message]
2010-05-14 19:22 ` bugzilla-daemon
2010-05-20  9:45 ` bugzilla-daemon
2010-05-20 23:26 ` bugzilla-daemon
2010-05-20 23:30 ` bugzilla-daemon
2019-11-19  8:12 ` bugzilla-daemon

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=20100514143200.2ED5913004E@annarchy.freedesktop.org \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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