Skip to content

properly destroying ffmpeg #41

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Roki100 opened this issue Feb 23, 2020 · 0 comments
Open

properly destroying ffmpeg #41

Roki100 opened this issue Feb 23, 2020 · 0 comments

Comments

@Roki100
Copy link

Roki100 commented Feb 23, 2020

Issue:

im getting Cannot call write after a stream was destroyed in discord.js after doing <prism ffmpeg>.destroy() on dispatcher finish event

Steps to reproduce:

use prism ffmpeg and pass it into dispatcher, then destroy this ffmpeg on disaptcher finish (without it, ffmpegs does not despawn)

Further details:

  • Operating System: windows 10 home
  • Node.js version: 12.4.1
  • Commit I'm using: prism 1.2.0 (that one that comes with discord.js master)

My reason of creating this issue

i cant seem to destroy ffmpeg without errors so my question is how can i destroy it properly
// it happens only while piping ytdl to transcoder, using -i url in ffmpeg doesnt throw that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant