Bug 10166

Summary:	xcb_ext.c: get rid of global lock in get_lazyreply
Product:	XCB	Reporter:	Ian Osgood <iano>
Component:	Library	Assignee:	Jamey Sharp <jamey>
Status:	RESOLVED MOVED	QA Contact:
Severity:	enhancement
Priority:	medium
Version:	1.0
Hardware:	All
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Ian Osgood 2007-03-02 21:38:41 UTC

There is a global lock that must be acquired any time an extension request is used, which protects a clause which only needs protection at the initialization of the extension in a process.  We should come up with a lockless design for this logic.

Comment 1 chemtech 2013-03-26 07:59:41 UTC

Ian Osgood, 
Do you still experience this issue with newer soft ?
Please check the status of your issue.
Or close this bug.

Comment 2 Ian Osgood 2013-03-26 14:24:02 UTC

Yes, that lock is still there six years later, as you can plainly see. :)

Neither Jamey nor I are active on the project, so this enhancement should be assigned to someone else. Who is the current XCB project lead? I nominate you, since you seem to care about this.

Comment 3 GitLab Migration User 2019-02-16 19:41:28 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/lib/libxcb/issues/26.

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.