Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • libX11 libX11
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 69
    • Issues 69
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • xorg
  • lib
  • libX11libX11
  • Merge requests
  • !29

Proper fix for the lockup in _XReply()

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Dmitry Osipenko requested to merge digetx/libx11:lockup-fix2 into master Oct 24, 2019
  • Overview 10
  • Commits 2
  • Changes 3

This a second attempt to fix #93 (closed) which turned out wasn't properly fixed by f5ba2c63. @sparaddi reported that there is a similar lockup to what I was initially experiencing in a form of recursive synchronization and then we found out that the real root of the problem is that _XError() uses wrong version of LockDisplay() that shall not be used when invoked from _XReply() because it may cause the offending re-syncing by sending request and getting reply within a reply.

Edited Nov 26, 2019 by Dmitry Osipenko
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: lockup-fix2