logger: Create only one Context per process for mobile #38149
Mobile/Perf (success)
Check has finished
Details
Check run finished (success ✔️)
The check run can be viewed here:
Mobile/Perf (pr/38149/main@c407e11)
Check started by
Request (pr/38149/main@c407e11)
c407e11 
#38149 merge main@ad2a1c7
logger: Create only one Context per process for mobile
The Logger::Context operates as a stack. When a new one is created, it becomes the active Context. When it gets destroyed, the destructor pops the previous Context as the currently active one.
This can lead to lifetime bugs in Envoy Mobile, if multiple engines are created and the destruction of those engines lead to indeterminate destruction of the Logger::Context objects.
In this commit, the behavior is changed so that the Logger::Context initialization is done by the external caller, not inside StrippedMainBase as previously done. This allows the caller, in this case, Envoy Mobile, to ensure only one Logger::Context is ever created, circumventing any potential issues on Context destruction with popping the previously saved context.
Environment
Request variables
| Key | Value |
|---|---|
| ref | d0da957 |
| sha | c407e11 |
| pr | 38149 |
| base-sha | ad2a1c7 |
| actor | @abeyad |
| message | logger: Create only one Context per process for mobile... |
| started | 1737758874.852263 |
| target-branch | main |
| trusted | false |
Build image
Container image/s (as used in this CI run)
| Key | Value |
|---|---|
| default | envoyproxy/envoy-build-ubuntu:d2be0c198feda0c607fa33209da01bf737ef373f |
| mobile | envoyproxy/envoy-build-ubuntu:mobile-d2be0c198feda0c607fa33209da01bf737ef373f |
Version
Envoy version (as used in this CI run)
| Key | Value |
|---|---|
| major | 1 |
| minor | 34 |
| patch | 0 |
| dev | true |