-
-
Notifications
You must be signed in to change notification settings - Fork 230
Fix/0.0.95 crashes #383
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
Merged
+104
−29
Merged
Fix/0.0.95 crashes #383
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
74902d2
fix(android): reduce LiteRT native crashes
dishit-wednesday c747d79
fix(android): fix double-close race in LiteRT conversation teardown
dishit-wednesday 4478a9c
show ui msg gpu is not supported on pixel 10
dishit-wednesday 6745ea1
reduce number of lines
dishit-wednesday bb37d8d
fix(android): guard null job in whisper realtime finish to prevent SI…
dishit-wednesday 2698cbc
improve pixel 10 warning ui
dishit-wednesday File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To prevent concurrent access and race conditions on the
conversationandenginelifecycles, we should introduce aMutexto synchronize these operations.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed differently —
stopGenerationno longer callscloseConversationSafelyat all. It now only signals stop synchronously:currentJob?.cancel()+conversation?.cancelProcess(). This eliminates the close/close race architecturally since onlyresetConversationandunloadModelever callclose(), and those are serialized viacurrentJob?.join()incloseConversationSafely.The remaining concurrent-close case (two
unloadModelcalls racing) is handled by@Volatileonconversationplus a null-first swap:val conv = conversation ?: return; conversation = null. Only one caller gets the non-null handle and proceeds toclose().A
Mutexhere would also need to guard theconversation = eng.createConversation()assignment inresetConversationto be correct — otherwise a concurrent caller can still acquire the lock after close and later close a freshly created conversation.