Skip to content

Conversation

@robsdedude
Copy link
Member

Writing to stdout in nodejs is done asynchronously. So when adding data to the queue faster than it can be flushed, the process will eventually crash because the system is running out of memory. By limiting the length of log messages, this problem can be avoided.

Writing to stdout in nodejs is done asynchronously. So when adding data to the
queue faster than it can be flushed, the process will eventually crash because
the system is running out of memory. By limiting the length of log messages,
this problem can be avoided.
Copy link
Contributor

@MaxAake MaxAake left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ 🙇🏻

@MaxAake MaxAake merged commit 11a74e4 into neo4j:6.x Aug 21, 2025
47 checks passed
@robsdedude robsdedude deleted the testkit/fix-logging-memory-clogging branch August 21, 2025 13:49
MaxAake pushed a commit that referenced this pull request Sep 16, 2025
Writing to stdout in nodejs is done asynchronously. So when adding data to the
queue faster than it can be flushed, the process will eventually crash because
the system is running out of memory. By limiting the length of log messages,
this problem can be avoided.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants