Fix late PJSUA2 object destroy on Android #3674
Merged
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.
audioDevMgr
(classDevAudioMedia
) is a member ofEndpoint
, so its destructor is executed after theEndpoint
destructor. When theDevAudioMedia
destructor invokesAudioMedia::unregisterMediaPort()
, exception is triggered when invokingEndpoint::instance()
, as theEndpoint::instance_
has been set toNULL
, and the exception invokespj_log()
while PJLIB has been deinitialized, so the assertion shown below occurs.The fix idea is simply to destroy
audioDevMgr
inEndpoint
destructor beforeEndpoint::instance_
is set toNULL
and before PJLIB is deinitialized.Here is the log and stack trace: