Skip to content

fix(gin): cap V8 CodeRange to 64MB on low-memory systems OS-21534#142

Merged
caneraltinbasak merged 1 commit into
42-x-y-bsfrom
cal/42-x-y-bs/low-memory-device-mem-alloc
Jun 4, 2026
Merged

fix(gin): cap V8 CodeRange to 64MB on low-memory systems OS-21534#142
caneraltinbasak merged 1 commit into
42-x-y-bsfrom
cal/42-x-y-bs/low-memory-device-mem-alloc

Conversation

@caneraltinbasak
Copy link
Copy Markdown

On ARM64 devices with ≤512MB physical RAM (e.g. BrightSign Pagani), V8's default 256MB CodeRange reservation exceeds CommitLimit.

Cap CodeRange to kMinimumCodeRangeSize (64MB) when physical memory is at or below 512MB. This allows the kernel to satisfy the mmap without requiring overcommit policy changes.

Also re-exports the ICU timezone patch to fix unrelated patch drift.

On ARM64 devices with ≤512MB physical RAM (e.g. BrightSign Pagani),
V8's default 256MB CodeRange reservation exceeds CommitLimit.

Cap CodeRange to kMinimumCodeRangeSize (64MB) when physical memory is
at or below 512MB. This allows the kernel to satisfy the mmap without
requiring overcommit policy changes.

Also re-exports the ICU timezone patch to fix unrelated patch drift.
@caneraltinbasak caneraltinbasak changed the title gin: cap V8 CodeRange to 64MB on low-memory systems OS-21534 fix(gin): cap V8 CodeRange to 64MB on low-memory systems OS-21534 Jun 4, 2026
@caneraltinbasak caneraltinbasak merged commit 5ea4c27 into 42-x-y-bs Jun 4, 2026
32 of 34 checks passed
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