[PAR-735] Fix memory exhaustion in LoggerService when logging complex objects#16
Merged
Merged
Conversation
Replace unbounded print_r() on context values with type-aware formatting: Throwable objects are serialized as "Class: message in file:line", other objects use json_encode with depth limit, scalars/arrays keep print_r. This prevents OOM when exceptions with large object graphs are passed as log context (PAR-735). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
1 participant
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 is the goal?
Fix memory exhaustion in LoggerService when logging complex objects
References
How is it being implemented?
Replace unbounded print_r() on context values with type-aware formatting: Throwable objects are serialized as "Class: message in file:line", other objects use json_encode with depth limit, scalars/arrays keep print_r. This prevents OOM when exceptions with large object graphs are passed as log context (PAR-735).
How is it tested?
Automatic tests
How is it going to be deployed?
Standard deployment