-
-
Notifications
You must be signed in to change notification settings - Fork 4
fix(jni): detach native threads and preserve callbacks #51
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
Open
AlexProgrammerDE
wants to merge
4
commits into
pschichtel:stable
Choose a base branch
from
enderdash-com:agent/fix-jni-thread-lifecycle-stable
base: stable
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
3744370
fix(jni): detach terminated native threads
AlexProgrammerDE 0bef6a5
fix(jni): harden JVM lifecycle transitions
AlexProgrammerDE 826d08b
fix(jni): retain peer callbacks through deletion
AlexProgrammerDE 55eeccb
test(jni): cover native lifecycle edge cases
AlexProgrammerDE 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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,14 @@ | ||
| #include "peer_connection_lifecycle.h" | ||
|
|
||
| #include "callback.h" | ||
| #include <rtc/rtc.h> | ||
|
|
||
| jint delete_peer_connection(JNIEnv* env, jint peer_handle) { | ||
| struct jvm_callback* callback = rtcGetUserPointer(peer_handle); | ||
| jint result = rtcDeletePeerConnection(peer_handle); | ||
| if (result == RTC_ERR_SUCCESS && callback != NULL) { | ||
| free_callback(env, callback); | ||
| } | ||
|
|
||
| return result; | ||
| } |
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,8 @@ | ||
| #ifndef LIBDATACHANNEL_JNI_PEER_CONNECTION_LIFECYCLE_H | ||
| #define LIBDATACHANNEL_JNI_PEER_CONNECTION_LIFECYCLE_H | ||
|
|
||
| #include <jni.h> | ||
|
|
||
| jint delete_peer_connection(JNIEnv* env, jint peer_handle); | ||
|
|
||
| #endif//LIBDATACHANNEL_JNI_PEER_CONNECTION_LIFECYCLE_H |
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.
When would either of this ever happen? Given that JNI_OnLoad would only ever be called once when loading the library.
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.
pthread_key_create can fail on its first invocation with EAGAIN or ENOMEM. That's why we validate it here.
The jvm NULL check is theoretically unnecessary, but it's just defensive validation. I can remove it if you want.
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.
well true, but is that likely to show up here? Have you seen these?