Fix: Replace Console Transport with File Transports to Prevent Memory Issues #2
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
fix memory leak
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.
This PR addresses a memory issue caused by the usage of the Console transport in production environments. According to the official documentation, using the Console transport in production is not recommended due to potential high memory usage.
Changes Made
error.log: Logs messages with an importance level oferroror less.combined.log: Logs messages with an importance level ofinfoor less.Testing
Verified that logs are correctly written to error.log and combined.log.
Confirmed that memory usage remains stable in a production-like environment.
Additional Notes
Please review the changes and let me know if there are any concerns or suggestions for further improvement.