public inbox for
help / color / mirror / Atom feed
From: Jon TURNEY <>
Subject: Re: problem with opengl (glxgears) running on cygwin ....
Date: Tue, 25 Mar 2014 14:05:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 20/03/2014 08:41, Linda Walsh wrote:
> When I try to run glxgears locally, it displays the initial gears,
> but now they are just frozen.  It doesn't work remotely, either,
> which was what I tried initially.  It *used* to work -- remotely
> at 20-30 frames/second (as measured by fraps).
> Interestingly enough, I get a glx window, -- fraps will display
> 30 (the right number for my screen refresh rate), in the right corner
> of the glxgears window... but the gears don't move.
> Same effect happens when I try remotely.  Window comes up with gears
> displayed, but no motion.  Fraps also shows 30 FPS.

Thanks for pointing out this issue.

I think that currently glxgears doesn't work very well with the combination of
indirect rendering and vsync-limited buffer swapping, so you are getting 30
fps, but they aren't useful frames.

Since [1], glxgears turns at a constant 70 degrees per second.

glxSwapBuffers does not block when used with indirect rendering, which means
that lots of frames can be rendered almost instantly, with no apparent
rotation, since the elapsed time between frames is very small.

glxgears is a very basic test that GLX is functioning, and definitely not a
benchmark.  Real GLX clients should have a better mechanism for ensuring their
animation rate doesn't outrun the vsync frequency.

If you have any problems with real GLX clients, I would be interested to hear


> When I try remote display, the above is pretty much the same except
> I get an error on the client system that it can't load the 3d
> driver on the other end.

There is some problem with loading the renderer on the remote
system, so it is falling back to indirect rendering.

What is the OS of the remote system?

> But it sees pretty much the same capabilities -- FWIW, there is next to zilch
> network traffic happening when I try this.. I mean while it is happening.
> Before and after ~ 200-400KB/s (xosview), during, all my X windows become
> very slow and no longer refresh steadily. Network throughput registers a drop
> to 1-80KB/s.  Despite that -- xwin pegs a cpu @100% and stays that way
> until I exit glxgears.

I think this is because glxgears will send frames as fast as it can, and can
saturate the X server.

Volunteer Cygwin/X X Server maintainer

Unsubscribe info:
Problem reports:

  reply	other threads:[~2014-03-25 14:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-20  8:41 Linda Walsh
2014-03-25 14:05 ` Jon TURNEY [this message]
2014-03-25 15:59   ` Linda Walsh
2014-03-27  6:28   ` Yaakov (Cygwin/X)
2014-03-27  7:33     ` remote desktop /session bus woes...(was Re: problem with opengl (glxgears) running on cygwin ....) Linda Walsh

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:

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

  git send-email \ \ \ \ \

* 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 read-only IMAP folder(s) and NNTP newsgroup(s).