[PR #1278] [MERGED] docs(ghidra): explain supported heap and CPU controls #2760

New issue

Closed

opened 2026-10-17 21:09:56 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-17 21:09:56 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/1278
Author: @N0zoM1z0
Created: 10/9/2026
Status: ✅ Merged
Merged: 10/9/2026
Merged by: @N0zoM1z0

Base: main ← Head: docs/ghidra-resource-controls

📝 Commits (4)

fa80b8b docs(ghidra): explain supported heap and CPU controls
a9dde30 Merge remote-tracking branch 'origin/main' into docs/ghidra-resource-controls
49b991b test(ghidra): select the batch fixture environment explicitly
2487292 Merge remote-tracking branch 'origin/main' into docs/ghidra-resource-controls

📊 Changes

1 file changed (+61 additions, -2 deletions)

View changed files

📝 docs/installation.md (+61 -2)

📄 Description

Explain the heap settings consumed by the Ghidra launcher, intentional JVM environment overrides, and the distinction between heap, process-family memory and CPU affinity. Correct the setup guide's claim that resource settings are entirely Ghidra defaults, and describe how to inspect the owned JVM rather than assume parent environment settings reached it.

Closes #1255. No runtime or provider capabilities change.

Validation: npm run docs:check passed under the bounded local guard. Cross-checked the POSIX launcher and installed Ghidra 12.1.4 Windows script. The existing real Linux Ghidra acceptance proof observed -Xmx512M, GC/compiler thread counts of 2 and the selected two-CPU affinity. No additional Windows/macOS Ghidra runtime verification or CPU/RSS performance claim is made for this documentation change.

The final branch incorporates current main and preserves the already merged #1281 correction to the Windows batch fixture. A real Windows smoke using the production launcher and identical fixture reproduced the empty-environment failure, passed with the explicit caller environment, and verified owned cleanup in both controls. No duplicate fixture change remains in this PR.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/1278 **Author:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Created:** 10/9/2026 **Status:** ✅ Merged **Merged:** 10/9/2026 **Merged by:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Base:** `main` ← **Head:** `docs/ghidra-resource-controls` --- ### 📝 Commits (4) - [`fa80b8b`](https://github.com/morluto/rea/commit/fa80b8bc5d99ce4227c8e3a90e3e0e5a1a6fbed2) docs(ghidra): explain supported heap and CPU controls - [`a9dde30`](https://github.com/morluto/rea/commit/a9dde3040ac01fa7b16b093721e98217928d91f7) Merge remote-tracking branch 'origin/main' into docs/ghidra-resource-controls - [`49b991b`](https://github.com/morluto/rea/commit/49b991bbf8e1b929123009ee47a9012e8938d2d5) test(ghidra): select the batch fixture environment explicitly - [`2487292`](https://github.com/morluto/rea/commit/2487292a6950fd4e9c2bb4e0b0357672af517588) Merge remote-tracking branch 'origin/main' into docs/ghidra-resource-controls ### 📊 Changes **1 file changed** (+61 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `docs/installation.md` (+61 -2) </details> ### 📄 Description Explain the heap settings consumed by the Ghidra launcher, intentional JVM environment overrides, and the distinction between heap, process-family memory and CPU affinity. Correct the setup guide's claim that resource settings are entirely Ghidra defaults, and describe how to inspect the owned JVM rather than assume parent environment settings reached it. Closes #1255. No runtime or provider capabilities change. Validation: `npm run docs:check` passed under the bounded local guard. Cross-checked the POSIX launcher and installed Ghidra 12.1.4 Windows script. The existing real Linux Ghidra acceptance proof observed `-Xmx512M`, GC/compiler thread counts of 2 and the selected two-CPU affinity. No additional Windows/macOS Ghidra runtime verification or CPU/RSS performance claim is made for this documentation change. The final branch incorporates current main and preserves the already merged #1281 correction to the Windows batch fixture. A real Windows smoke using the production launcher and identical fixture reproduced the empty-environment failure, passed with the explicit caller environment, and verified owned cleanup in both controls. No duplicate fixture change remains in this PR. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-17 21:09:56 +00:00