Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • pipewire pipewire
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 584
    • Issues 584
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 23
    • Merge requests 23
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PipeWirePipeWire
  • pipewirepipewire
  • Issues
  • #565
Closed
Open
Issue created Jan 11, 2021 by hexchain@hexchainContributor

Client should not crash the server

Ideally, a client should not be able to crash the server on any occasion. However, currently there are multiple ways to crash the server with just pw-cli:

  • pw-cli d 2 (deletes libpipewire-module-protocol-native)
  • pw-cli d $(pw-cli dump short | grep pw-cli | cut -d':' -f1) (deletes the pw-cli client itself)
  • pw-cli d 5 twice (deletes libpipewire-module-metadata)
Assignee
Assign to
Time tracking