TLDR: when reading context from FeatureScope triggers a context update which again publishes context updates again to all the subscribes and we end up in a loop.
This shoots up CPU usage and an app termination likely.
How?
Now, when we read the context, we no longer update it.
a small improvement in WT message receiver
There a few learnings from this bug
The current pub-sub mechanism is very complex and requires a lot of dive deep before you can start making sense.
The value pub-sub delivers to its consumers is very simple which we have talked before also. For example, on every context, telemetry, webview or baggage message, each receiver is notified which is wastage of CPU cycles. The receivers must be able to subscribe to individual message or part of message.
Review checklist
[ ] Feature or bugfix MUST have appropriate tests (unit, integration)
[ ] Make sure each commit and the PR mention the Issue number or JIRA reference
What and why?
TLDR: when reading
contextfromFeatureScopetriggers a context update which again publishes context updates again to all the subscribes and we end up in a loop.This shoots up CPU usage and an app termination likely.
How?
There a few learnings from this bug
Review checklist