Skip to content
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

Properly handle despawned entities with Process component #12

Open
edouardpoitras opened this issue Jan 9, 2024 · 2 comments
Open

Properly handle despawned entities with Process component #12

edouardpoitras opened this issue Jan 9, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@edouardpoitras
Copy link
Owner

We need to ensure that if an entity with a Process component is despawned, that the underlying process is killed (or at least document the behavior appropriately).

On Linux, it seems the process would continue running in the background and no ProcessCompletedEvent or ProcessOutputEvent would be generated any more. Once Bevy exits, the process would terminate.

This behavior could be different on Windows, remains to be tested.

@edouardpoitras edouardpoitras changed the title Properly deal with despawned entities with Process component Properly handle despawned entities with Process component Jan 9, 2024
@TimJentzsch TimJentzsch added the bug Something isn't working label Jan 9, 2024
@TimJentzsch
Copy link
Collaborator

The component lifecycle hooks have been merged, so we can probably tackle this once Bevy 0.14 is released

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants