JOJ3 itself will be killed due to OOM when copyOut files are large #86
Labels
No Label
bug
component
executor
component
framework
component
parser
component
UI
duplicate
enhancement
help wanted
invalid
priority
p0
priority
p1
priority
p2
priority
p3
question
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: JOJ/JOJ3#86
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As described in https://docs.goj.ac/design#memory-usage, it should be fine when /dev/shm has 8G and memory has 16G on joj-dev. But in practice, 100 cases of 1M copy out stdout & stderr will cause JOJ3 oom.
It relates to running JOJ3 in act_runner. Run JOJ3 directly on joj-dev will not cause OOM but inside act_runner it will.
Fixed in
07cbf29792
.os/exec
in golang does not fork the process, so rlimit will be applied to the current parent process. Check https://www.reddit.com/r/golang/comments/inpsqv/how_to_limit_memory_usage_in_a_child_process/.