Skip to content

fix: increase sim ram to avoid crashes in contact rich scenes - #9

Draft
juelg wants to merge 2 commits into
masterfrom
fix/mujoco-arena-memory
Draft

juelg wants to merge 2 commits into
masterfrom
fix/mujoco-arena-memory

Conversation

@juelg

@juelg juelg commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor
  • removed asset version check which is now handled by rcs
  • set mujoco ram which is now supported by rcs
  • bump rcs version

blocked until rcs is released to 0.7.4

juelg added 2 commits October 20, 2026 22:01
rcs-core 0.7.4 versions the asset cache itself (assets/.version, atomic
download), so the duobench-side marker and get_prefix bypass are no longer
needed. With 0.7.4 they would even keep stale assets: a DUOBENCH_PREFIX with
only the duobench marker counts as user-provided for rcs and is not refreshed.
MuJoCo sizes the arena from the scene at rest (15-22 MiB for the DuoBench
scenes). Contact-rich episodes exceed it, e.g. ball_maze evals with ~170
contacts and ~1100 constraint rows abort with "mj_stackAlloc: insufficient
memory".

Use 256 MiB via SimConfig.memory (rcs-core 0.7.4) for all DuoBench scenes.
The value is set in the scene config and also applied at env creation when
sim_cfg.memory is still automatic, since eval setups commonly replace
sim_cfg with a fresh SimConfig; an explicitly set value is kept.

This branch has not been deployed

No deployments
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.

1 participant