I'm seeing some errors like this when using the ECS run launcher, where most of the ops in a dynamic mapping step fail like this:

Multiprocess executor: child process for step run_concordance_by_chrom[17] unexpectedly exited with code -9
dagster.core.executor.child_process_executor.ChildProcessCrashException

Stack Trace:
  File "/usr/local/lib/python3.9/site-packages/dagster/core/executor/multiprocess.py", line 210, in execute
    event_or_none = next(step_iter)
,  File "/usr/local/lib/python3.9/site-packages/dagster/core/executor/multiprocess.py", line 323, in execute_step_out_of_process
    for ret in execute_child_process_command(multiproc_ctx, command):
,  File "/usr/local/lib/python3.9/site-packages/dagster/core/executor/child_process_executor.py", line 163, in execute_child_process_command
    raise ChildProcessCrashException(exit_code=process.exitcode)

is this indicative of a processes getting killed from too much memory usage?

Hi Zach - running out of memory is the mostly likely culprit here, yeah

thanks - indeed it appears that increasing the memory via the ecs/memory run tag has solved the issue