-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Fix actuator gain snapshot corruption for multi-env floating-base articulations #6407
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
AntoineRichard
merged 1 commit into
isaac-sim:develop
from
AntoineRichard:antoiner/fix-actuator-gain-env-stride
Jul 9, 2026
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
12 changes: 12 additions & 0 deletions
12
source/isaaclab_newton/changelog.d/fix-actuator-gain-env-stride.rst
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,12 @@ | ||
| Fixed | ||
| ^^^^^ | ||
|
|
||
| * Fixed the initial actuator gain snapshot used by | ||
| :func:`~isaaclab.envs.mdp.events.randomize_actuator_gains` corrupting (or | ||
| crashing) for multi-environment floating-base articulations with Newton | ||
| actuators. The per-environment stride of the actuator DOF indices was | ||
| decoded with the articulation-local joint count instead of the whole | ||
| model's per-environment DOF count, so on a floating base the free-root DOFs | ||
| shifted every environment past the first to the wrong (or out-of-bounds) | ||
| snapshot rows, corrupting the ``stiffness`` / ``damping`` randomization | ||
| baseline. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
4 changes: 4 additions & 0 deletions
4
source/isaaclab_physx/changelog.d/fix-actuator-gain-env-stride.skip
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,4 @@ | ||
| Adapts the PhysX Newton-actuator call site to the new required ``env_stride`` | ||
| argument of ``build_newton_actuator_defaults``. No user-facing behavior change: | ||
| PhysX articulations have no free or ball joints, so the per-env DOF stride | ||
| already equals the articulation-local joint count. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cuda:0The PR description explicitly calls out the CPU failure mode (glibc
corrupted size vs. prev_size→ deterministic SIGABRT) as a separate, more visible symptom of the same OOB write. The new test is hardcoded todevice="cuda:0", so a CPU-only CI runner would never exercise this path. If the test suite has a mechanism to parameterize over devices, adding a"cpu"variant here would directly cover the documented CPU crash scenario.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!