gtk+ and randr
airlied at gmail.com
Mon Jul 21 14:46:11 PDT 2008
On Tue, Jul 22, 2008 at 7:39 AM, Soeren Sandmann <sandmann at daimi.au.dk> wrote:
> Adam Jackson <ajax at nwnk.net> writes:
>> On Sun, 2008-07-20 at 16:40 -0400, Ben Gamari wrote:
>> > Howdy all,
>> > As many of you probably know, GTK+ has apparently been calling
>> > XRRGetScreenResources() on startup for some time now. Having a laptop, I
>> > occasionally find myself using VGA displays which, for the last few
>> > months, flickered horribly when starting a gtk+ application due to EDID
>> > probing (as I reported in bug #16224 ). Earlier this week, this issue
>> > was worsened when I pulled down the latest xorg commits from git. On my
>> > intel hardware, even the LVDS output now flickers when starting a gtk+
>> > application.
>> XRRGetScreenResources is an expensive call. Always. If gtk is calling
>> it on every app startup they're absolutely insane.
> I don't know any reason it has to be expensive or flicker, and if it
> has to, then we have a problem, because at login time we do need to
> call it to set the user's screen configuration; there is no way around
> it. On most hardware I have tried it on, it hasn't been all that
It not bounded however.. if you have lots of outputs in the future and have
to probe them this is going to be linear..
More information about the xorg