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.

Sign up for GitHub

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

Jump to bottom

Socket-child can be left orphaned on parent crash #30

Closed
Julusian opened this issue Oct 19, 2018 · 1 comment
Closed

Socket-child can be left orphaned on parent crash #30

Julusian opened this issue Oct 19, 2018 · 1 comment

Comments

@Julusian
Copy link
Member

  • I'm submitting a ...
    [*] bug report

  • Summary
    I noticed today that I had a few socket-child processes running on my system with no node processes running that would be utilising an atem-connection.
    image
    I have tried to reproduce this and have managed to do so if the parent application crashes with an unhandled exception, but there could be other ways of achieving the same result.

I'm not sure how the memory usage got so high. I suspect that they have been running for a few days and have a huge number of commands to send to the parent buffered.
mint-dewit pushed a commit that referenced this issue Oct 24, 2018
fix: socket process exits when parent process does (#30)
4754cc7
@mint-dewit
Copy link
Member

Tested in Ubuntu 18.04 and fixed in atem-connection 0.7.0

Please reopen if the issue occurs again!

@Julusian Julusian mentioned this issue Dec 3, 2018
Closed
@Julusian Julusian mentioned this issue Nov 22, 2019
Closed
@Julusian Julusian mentioned this issue Dec 7, 2019
Merged
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Julusian @mint-dewit