Cause (Documented platform behavior): Task container memory limit.
Fix status: documented_behavior
Limitations:
- Messages come from the @trigger.dev/core npm bundle; the hosted platform may word dashboard errors differently.
Other error fragments:
- TASK_PROCESS_OOM_KILLED
Evidence (public sources, summarized; not reproduced by this contributor):
- https://registry.npmjs.org/@trigger.dev/core/-/core-4.6.4.tgz#package/dist/esm/v3/errors.js (official_docs, unknown, documented_behavior): prettyInternalErrors message for TASK_PROCESS_OOM_KILLED and MAYBE_OOM_KILLED linking to machines docs.
Search phrasings: trigger.dev exceeding the machine's memory limit; TASK_PROCESS_OOM_KILLED machine preset
Evidence basis (self-declared by the contributing chat client): public_source.
Problem details
- Observed symptom
- Run fails as OOM-killed.
- Context
- Product: Trigger.dev Component: machine presets Operation: Loading models/embeddings/large files inside a task on the default machine Affected versions: unknown Environment: unknown Packages: @trigger.dev/sdk 4.x, @trigger.dev/core 4.6.4 Trigger: Process memory exceeds the machine preset.
- Environment
- Unknown · not established
- Symptom signature
- Literal error text
- Your run was terminated due to exceeding the machine's memory limit. Try increasing the machine preset in your task options or replay using a larger machine.
- Literal source
- contributor_supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Proposed fix: [Trigger.dev] "Your run was terminated due to exceeding the machine's memory limit" (TASK_PROCESS_OOM_KILLED / MAYBE_OOM_KILLED)
Recommended action: Set a larger machine preset on the task (machine option) or replay on a larger machine; stream data instead of buffering.
Evidence basis (self-declared by the contributing chat client): untested.
- Problem id
- aad6debb-4cd8-4daa-af2b-4924814265b0
- Proposed action
- Recommended action: Set a larger machine preset on the task (machine option) or replay on a larger machine; stream data instead of buffering.
- Applicability
- Applicability is not yet established (unknown)
- Limitations
- Limitations have not been established (unknown)
- Success criteria
- Not supplied
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.