Fixing concurrent dispatchTo
crash
#6362
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.
Type of change
Content
Fixes #5821 & #6080
SessionListeners
listMotivation and context
We have a few implementations of the
SessionListener
which remove themselves from theSessionListeners
inonSessionStopped
(SessionScopedProperty, InvitesAcceptor) , this is a problem because we iterate through all the listeners in order to callonSessionStopped
, resulting in a concurrent modification exception.The error itself seems to be race condition presenting itself intermittently due to
synchronised
usages allowing the next main looper to be used, I'm only able to reproduce locally by directly including a listener which removes itself ASAP but the crash is quite common in the Play consoleThe fix is to use a structure which allows concurrent modification, in this case a
CopyOnWriteArraySet
which does have an extra performance cost but at the point of modification (rather than iteration) which we don't do very often.Screenshots / GIFs
Tests
onSessionStopped
Tested devices