termux-tts-speak crashes when multiple instances are executed
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.3k
- Forks
- 920
- PR merge metrics
- No merged PRs in 30d
Description
I have made a script that reads messages in a groupchat with different voices for different persons using termux, termux-tts-speak, acapela voices, ii, hangups, pickups inotifywait and a bash script of my own.
It works okay, but if two people say something too soon after eachother, then two instances of termux-tts-speak will be executed at the same time and it seems to crash the whole voice synth thing.
Is this a limitation of android? or is there some sort of bug in termux? If it is as i suspect a limitation of android, would it be possible to make termux-tts-speak check if another instance of itself is running before starting and if so it will wait a few seconds and try again until no other instances are running.
Would be great because its annoying when it crashes if the script runs too soon or fast.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Use termux-tts-speak as the entry point and reproduce the failure by launching multiple instances close together. Determine whether concurrent invocations fail consistently, then verify that the completed behavior handles overlapping calls without crashing the voice synthesis process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- cli, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100