Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • W weston
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 316
    • Issues 316
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 118
    • Merge requests 118
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • wayland
  • weston
  • Issues
  • #322

Closed
Open
Created Dec 01, 2019 by Pekka Paalanen@pqMaintainer

Use wl_global_remove in libweston

Instead of having core, plugins, whatever call wl_global_create() and wl_global_destroy() directly, offer an API that wraps a struct wl_global and uses wl_global_remove() from wayland!28 (merged) under the hood to prevent clients racing with the removal. Naturally this requires tracking the new structs in struct weston_compositor and the associated timeout to finally destroy them after removal.

Use this new API for all wl_globals everywhere in the Weston repository.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking