This repository was archived by the owner on Jun 19, 2025. It is now read-only.
Open
Conversation
Contributor
|
Could you please consider merging this, @reuben? Thanks! |
Contributor
|
I no longer have push access to this repository. If you can open the PR against our coqui-ai/STT fork I'm happy to merge it. |
Author
|
Few weeks ago I was planning to do that (opening a PR against coqui). But failed to build the iOS static framework -- bazel prompts:
Will give it another try later. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hello,
This PR is an attempt to fix a double deallocation issue in the Swift client.
How to produce
let result = stream.finishStream()withlet result = stream.finishStreamWithMetadata(numResults: 1)DeepSpeechStreamis deallocated. In my case, Xcode prompted something like "Thread XXX: Deallocation of freed memory".References
Fix
Seems the fix can be as simple as adding one line of code. After the patch, the code pattern of
finishStreamWithMetadata(numResults:)now aligns withfinishStream().Thank you
Would like to thank @reuben for the Swift wrapper-related work!