Fix huge memory consumption for logging #458
Merged
Conversation
This file contains 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
ziegler-daniel
force-pushed
the
bugfix/huge_memory_consumption
branch
from
feda978 to
199138e
Compare
ziegler-daniel
force-pushed
the
bugfix/huge_memory_consumption
branch
from
199138e to
5e68cf9
Compare
maaaNu
approved these changes
Dec 16, 2024
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.
Logging of some objects (e.g.
AxiosError) withinspectand the options{ depth: null, maxArrayLength: null, maxStringLength: null }can cause a huge memory consumption as the strings become very large. Therefore, I switched back to the default limits ofinspect.