ES /docs

ChildProcessManager::setupEventHandlers | Child process stderr: <--- JS stacktrace --->

Service
cupixworks-any-bimrevision-agent
Occurrences
3
Status
Reported
Confidence
80%
Actionability
36%
Cluster ID
2679796a-0ed3-4178-b681-53b856864363
First Seen
2026-07-21 12:00 UTC
Last Seen
2026-07-23 11:08 UTC
Actions

ChildProcessManager::setupEventHandlers | Child process stderr: <--- JS stacktrace --->

What Happened#

2026-07-21 21:00:39 KST, cupixworks-any-bimrevision-agentBimCompareProcess child process 가 V8 heap out-of-memory 로 fatal error 를 던지고 종료되었다. 부모 서비스의 ChildProcessManager 는 child 의 stderr(FATAL ERROR: Ineffective mark-compacts near heap limit) 를 error 로그로 흘렸고, 이 stderr 스택트레이스가 25 개의 error cluster (본 클러스터 포함) 로 분류되었다. 실질적으로는 하나의 child 크래시이며, clark-vdc 팀이 요청한 대형 BIM revision 비교(154,331 entities) 처리 중 발생했다.

Quick Facts#

Field Value
exception.class FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
exception.message Child process stderr: <--- JS stacktrace --->
top_frame packages/base/src/manager/child-process.manager.ts:140 (stderr handler)
runtime Node.js (V8 heap limit ~8192 MB via --max-old-space-size=8192)
env production, us-west-2, tenant cupix

Affected Teams#

Team / Domain Error Count Impact
clark-vdc (bim-revision) 25 clusters, single crash 하나의 BIM revision 비교 job 실패 (revision comparison 결과가 Error 상태로 기록됨)

Timeline#

  1. 2026-07-21 20:53:10 KSTBimRevisionService::runBimCompare | begin — 부모 서비스가 child 로 비교 요청 시작
  2. 2026-07-21 20:53:11 KSTrunBimCompare | params - query.entities.length: 154331, checkExistence.length: 57346 — 대형 페이로드 전송
  3. 2026-07-21 21:00:39 KSTChild process stderr: FATAL ERROR: Ineffective mark-compacts near heap limit — V8 이 7909→7916 MB 근처에서 mark-compact 반복 실패 후 OOM abort
  4. 2026-07-21 21:01:45 KSTChild process closed, Process killed by signal SIGABRT — child 종료, 부모의 rejectAllPending 이 실행되고 BimRevisionService::run | error: "Process killed by signal SIGABRT" 로 revision 상태가 Error 로 마감

Scoring#

Confidence 80% · Actionability 36%

Confidence#

Dimension Score Detail
Evidence completeness 5/5 16 code refs, 5 log queries
Code path explicitness 3/3 16 file:line refs
Log evidence 2/3 section, query
RCA structure 3/3 3/3 sections
Revision history 0/3 0 revision(s)
Agent execution 3/3 success

Actionability#

Dimension Score Detail
Fix complexity 1/5 critical
Affected files 1/5 21 file(s)
Single repo 1/3 5 service(s)
Immediate actions 0/3 absent
Testability 0/3 no test info
External dependency 3/3 no external deps
Data migration 3/3 no migration