RUM-1042 Fix base64 issues with multithreading#1613
Merged
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #1613 +/- ##
===========================================
+ Coverage 83.55% 83.63% +0.07%
===========================================
Files 452 452
Lines 15625 15635 +10
Branches 2321 2320 -1
===========================================
+ Hits 13055 13075 +20
+ Misses 1948 1937 -11
- Partials 622 623 +1
|
jonathanmos
force-pushed
the
jmoskovich/rum-1042/fix-multithreading
branch
from
September 12, 2023 12:48
d36bc38 to
224ee66
Compare
jonathanmos
marked this pull request as ready for review
September 12, 2023 13:23
mariusc83
requested changes
Sep 12, 2023
jonathanmos
force-pushed
the
jmoskovich/rum-1012/fix-rippledrawables
branch
from
September 13, 2023 12:56
3b0b069 to
6e89a6d
Compare
jonathanmos
force-pushed
the
jmoskovich/rum-1012/fix-rippledrawables
branch
from
September 13, 2023 13:20
6e89a6d to
ffb98cd
Compare
jonathanmos
force-pushed
the
jmoskovich/rum-1042/fix-multithreading
branch
from
September 13, 2023 13:29
6af6ffa to
d1d73a2
Compare
Base automatically changed from
jmoskovich/rum-1012/fix-rippledrawables
to
develop
September 14, 2023 06:49
jonathanmos
force-pushed
the
jmoskovich/rum-1042/fix-multithreading
branch
2 times, most recently
from
September 14, 2023 08:09
26b4022 to
a48b1a3
Compare
0xnm
previously approved these changes
Sep 14, 2023
0xnm
approved these changes
Sep 14, 2023
mariusc83
approved these changes
Sep 14, 2023
jonathanmos
force-pushed
the
jmoskovich/rum-1042/fix-multithreading
branch
from
September 14, 2023 11:52
f9121d4 to
c22eb48
Compare
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
Fixes two issues that were discovered during functional tests.
The first issue is having the
AsyncImageProcessingCallbackheld by theBase64Serializerinstance, and this can lead to the next bitmap replacing the callback before the first one has completed. This can lead to the decrement of pending images happening on the wrong node. Solution: passing the asyncCallback in every call to handleBitmap.The second issue is having the previous
RumContextheld by theRumContextDataobject. This can lead to an item being removed from the queue (lost - not processed) with prevContext A and newContext B, and the next item with prevContext B newContext B will no longer be seen as a new view - so no meta data. Solution: the RecordedDataProcessor now holds it's own prevRumContext variable and replaces it only after processing an item.Motivation
Issues found during functional tests.
Additional Notes
Anything else we should know when reviewing?
Review checklist (to be filled by reviewers)