case-study 2026-10-10 case-studylinuxfedoraops

REA on Fedora: Node 22/24/26 timings & Linux notes

Linux hosts still surprise people. A detailed Fedora-based Discussion records **new Node medians** on a real Electron launcher and ties Ghidra, Chromium, and temp-path pitfalls back to actionable setup.

Source meta

— GitHub stars (snapshot)

Language: —

License: —

Updated: 2026-10-09

GitHub source ↗

rea.run rating

4/5 — Actionable Fedora field notes

Quality. Node 22/24/26 timings on a real Electron launcher; Ghidra/Temurin/Chromium notes.

Evidence. Public Discussion with tables + links to related issues/PRs.

Limits. One machine’s medians — not a universal benchmark.

For. Linux packagers and Fedora-family hosts running REA.

What it is. Show-and-tell notes from running REA 6.3.0 on a Fedora-family box: Node 22 vs 24 vs 26 medians for analyze-javascript-application, Ghidra 12.1.4 + Temurin JDK 21, Chromium via REA_BROWSER_EXECUTABLE, and short-TMPDIR advice.

Relation to REA. Direct field feedback into upstream issues/PRs; pairs with our /docs/linux-fedora/ guide.

Workflow. Match a supported Node line → export Ghidra/JAVA_HOME → point browser executable → keep TMPDIR free of problematic layouts → doctor before blaming the agent.

Evaluation. High signal for operators. Treat timings as one machine’s story; re-measure on yours.

Compliance

Notes use an authorized BAR launcher (MIT/Flathub packaging). Ops write-up, not a crack guide.

Takeaways

Newer Node helped median JS analysis time here.
Browser + Ghidra paths are the usual Linux snags.
Cross-link TMPDIR FAQ when doctor looks fine but analysis fails.

Related on rea.run