Assertion 'pthread_mutex_unlock(&m->mutex) == 0' failed at pulsecore/mutex-posix.c:108, function pa_mutex_unlock(). Aborting.

[windrunner414]

Build 17092.
I install vscode on ubuntu and i run it successfully.But when i reboot windows,I run vscode and it prints
Assertion 'pthread_mutex_unlock(&m->mutex) == 0' failed at pulsecore/mutex-posix.c:108, function pa_mutex_unlock(). Aborting.
Why?i can run it before.
I've already used the latest windows insider preview

[therealkenc]

#2819 #2760 (message) #1006 #486

[windrunner414]

@therealkenc But I've already update windows.And I can run it.

[windrunner414]

@therealkenc And when i restart it,and 'Assertion 'pthread_mutex_unlock(&m->mutex) == 0' failed at pulsecore/mutex-posix.c:108, function pa_mutex_unlock(). Aborting......'

[therealkenc]

#1006 and #486 are still open so updating Windows will not address your error. Your options are (1) don't install PulseAudio, (2) sudo apt purge libpulse0, (3) install the WSL PulseAudio PPA. If you have further questions regarding pulsaudio you can ask in #486 and someone may jump in to help. There is also discussion thread on VSCode at #2760.

[windrunner414]

@therealkenc ok,thank u

[cuprousoxide]

@therealkenc hey pardon the noob question, what do I do after I add the PPA and your repository to apt?

[therealkenc]

The PPA is stale at the moment, so for those wanting sound you're better off on 17627. It will probably hit regular Insiders RSN. On the Windows side, you need this. The hang out for the whole topic is #486.

[NicWickman]

This

Assertion 'pthread_mutex_unlock(&m->mutex) == 0' failed at pulsecore/mutex-posix.c:108, function pa_mutex_unlock(). Aborting. bug is causing me real issues.

I am trying to develop mobile applications, and emulators require that I run Pulseaudio...but having pulseaudio installed prevents me from opening VSCode or Atom, so it's a bit of a catch-22. I can't run an emulator and an IDE at the same time.

Like you mentioned kenc, the PPA is stale. I'm installing 17627 right now, but can you confirm that this issue is really solved if I update?