Skip to content

GitLab

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

Merged
Created Jan 03, 2019 by Sebastian Dröge@slomo🍵Owner

wasapisink: Don't call CoUninitialize() twice in unprepare()

  • Overview 3
  • Commits 1
  • Pipelines 2
  • Changes 1

It has to be symmetric with CoInitialize(), otherwise everything else will fail.


@nirbheek

I'm not sure why we uninitialize/initialize in unprepare/prepare if we already do the same in finalize/init. It's refcounted so the ones in unprepare/prepare should have no effect?

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: wasapisink-coinitialize