Bug 43667

Summary: Missing INTEL_swap_event at early stage in X startup
Product: xorg Reporter: Lionel Landwerlin <lionel.g.landwerlin>
Component: Driver/intelAssignee: Chris Wilson <chris>
Status: RESOLVED INVALID QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium    
Version: 7.5 (2009.10)   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Lionel Landwerlin 2011-12-09 07:03:28 UTC 
When fast booting on MeeGo, we launch the X server and quickly spawn all the first apps we want to display on the home screen as well as the window manager.

Our problem is that some of the apps we launch do not get a INTEL_swap_event event after the first glXSwapBuffers() call when they're launched early after X is started.

As we try to throttle the drawing, and do not re-swap the buffers as long as we haven't seen an acknowledgement of the previous swap, we end up with applications that never display anything.

If we wait for the first X event to call glXSwapBuffers(), then everything is fine.

We're using the X server 1.9.0 with some patches (as you can see) :

http://build.meego.com/package/files?package=xorg-x11-server&project=MeeGo%3A1.2.0%3Aoss%3AUpdate%3ATesting

I can point to images to reproduce the problem (sadly intel internal for now, but all the packages/sources to build them are available on build.meego.com), this is reproducable on a netbook like Asus X101.
Comment 1 Jeremy Huddleston Sequoia 2012-01-02 12:57:29 UTC 
You're using quite dated versions.  Can you please confirm that this issue still exists with the 1.12 RC and current intel drivers?
Comment 2 Lionel Landwerlin 2012-11-20 18:33:40 UTC 
Sorry, I can't really test that issue with latest drivers/X.
Feel free to close if you think this is now irrelevant.
Comment 3 Chris Wilson 2012-11-21 11:24:11 UTC 
If we aren't in a position to reproduce, then I guess we are not going to track down where the event disappears.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.