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

Sound_play node becomes invalid after running for a while #167

Closed
itohdak opened this issue Jun 18, 2019 · 1 comment
Closed

Sound_play node becomes invalid after running for a while #167

itohdak opened this issue Jun 18, 2019 · 1 comment

Comments

@itohdak
Copy link
Contributor

itohdak commented Jun 18, 2019

There has been an issue that sound_play node becomes invalid after running for a while.
I found two following causes for this issue.

This issue aims the latter.
I found that the rosservice call correctly printed the response but didn’t exit and kept holding the control, just before sound_play node for Japanese became stuck.
I think this issue relates with this.

Instead of debugging the rosservice call source, I tried to call the service through Python node, not through bash command in #166.

Are there any other solutions for this issue?

@itohdak
Copy link
Contributor Author

itohdak commented Jun 18, 2019

I have applied and tested the PR with the robot for some months, not facing the problem for now on.

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