Codegen leaves one folder per library in $TMPDIR on every pod install and Xcode build: generateCode never removes its mkdtempSync folder
Maintainer antworten meist innerhalb von 2 Tagen
Bewertung
- Schwierigkeit
- 2/5
- Geschätzter Aufwand
- 1-3 Stunden
- Anfängerfreundlichkeit
- 35/100
- Issue-Typ
- Bug
- Klarheit
- Klar beschrieben
- Aktivitätsstatus
- Veraltet
- Tech-Stack
- javascript, node.js, react-native
- Bereich
- build-system, mobile
Rechercherichtung
Start in packages/react-native/scripts/codegen/generate-artifacts-executor/generateNativeCode.js, especially generateCode and its mkdtempSync call. Check how the temporary directory is handled when generation succeeds or throws, then run the linked reproducer with TMPDIR, TEMP and TMP set to an empty folder. Done means no temporary folders remain and generated output is unchanged; pull request #60058 is already open against this issue.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Description
Every run of scripts/generate-codegen-artifacts.js, which pod install and Xcode's [CP-User] Generate Specs phase both run, leaves one folder per codegen library in the system temp folder ($TMPDIR on macOS), named after the library (AppSpecsXXXXXX, safeareacontextXXXXXX), each holding a copy of that library's generated code. Nothing removes them, so they add up with every pod install and every build.
On main (4a82359d7c), generateCode creates the folder with fs.mkdtempSync(path.join(os.tmpdir(), libraryName)), generates into its out/, copies that to the output folder with cpSyncRecursiveIfChanged, and returns without removing it. The file is the same in 0.88.1.
On a Mac with React Native 0.88.1 (macOS 27.2.1, Xcode 27.2, CocoaPods 1.17.0), one App Store build of an app with eleven codegen libraries left eleven folders from pod install and eleven more from xcodebuild archive, 12 KB to 1.3 MB each, and four days of builds had left 263 of them in that $TMPDIR.
Expected: the temporary folder is gone once generateCode has copied its files, whether generation succeeds or throws, and the output folder gets the same files as today.
Steps to reproduce
- Clone the reproducer below.
ReproducerApp/package.jsondeclares one app-level codegen library,AppSpecs, whose spec isReproducerApp/specs/NativeSample.ts. - In
ReproducerApp, runyarn install, thennode repro.js. It runsreact-native/scripts/generate-codegen-artifacts.js --path . --outputPath <output> --targetPlatform ios, the command Xcode's Generate Specs phase runs, withTMPDIR,TEMPandTMPpointed at an empty folder, and lists that folder after the codegen exits. It exits 1 while the codegen leaves anything there, 0 once it leaves nothing. - Expected: the folder is empty. Actual: it holds one folder per codegen library:
TMPDIR after the run holds 2 entries AppSpecsgxi4vl (3 files) safeareacontextEGhhho (14 files) DEFECT: codegen left 2 temporary folder(s) in TMPDIR after it exited
React Native Version
0.88.1
Affected Platforms
Build - MacOS, Build - Windows
Areas
Codegen
Output of npx @react-native-community/cli info
System:
OS: Windows 11 10.0.26300
CPU: "(32) x64 AMD Ryzen 9 9950X3D 16-Core Processor "
Memory: 139.30 GB / 255.67 GB
Binaries:
Node:
version: 26.12.1
path: C:\Program Files\nodejs\node.EXE
npm:
version: 12.2.1
path: C:\Program Files\nodejs\npm.CMD
Stacktrace or Logs
react-native 0.88.1, node v26.12.1, win32 10.0.26300 x64
TMPDIR, TEMP and TMP set to an empty folder
$ node react-native/scripts/generate-codegen-artifacts.js --path . --outputPath <output> --targetPlatform ios
[Codegen] Generating Native Code for AppSpecs - ios
[Codegen] Generated artifacts: <output>\build\generated\ios\ReactCodegen
[Codegen] Generating Native Code for safeareacontext - ios
[Codegen] Generated artifacts: <output>\build\generated\ios\ReactCodegen
codegen exited 0 and wrote 2 files to <output>/build/generated/ios/ReactCodegen/AppSpecs
TMPDIR after the run holds 2 entries
AppSpecsgxi4vl (3 files)
safeareacontextEGhhho (14 files)
DEFECT: codegen left 2 temporary folder(s) in TMPDIR after it exited
MANDATORY Reproducer
https://github.com/YevheniiKotyrlo/rn-codegen-tmpdir-repro
Screenshots and Videos
No response
- Vorherrschende Sprache
- C++
- Sterne
- 127k
- Forks
- 25.5k
- Ø Merge
- 3 T. 22 Std.
- Gemergte PRs (30 T.)
- 235
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus react/react-native
-
Needs: Author Feedback Needs: Repro
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
react/react-native#60059 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 2 Tagen
-
Needs: Triage :mag:
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100
react/react-native#60000 ·
Maintainer antworten meist innerhalb von 2 Tagen
-
`yarn test-ios` exits before building RNTester: `objc-test.sh` launches the WebSocket server script #59433 deletedEvtl. vergeben @lazerg hat das vor 4 Tagen übernommen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
react/react-native#59939 ·
Maintainer antworten meist innerhalb von 2 Tagen
-
iOS Fabric pointer-handler reset leaves the next lone touch non-primaryEvtl. vergeben @alleneubank hat das vor 6 Tagen übernommen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
react/react-native#59919 ·
Maintainer antworten meist innerhalb von 2 Tagen
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100
react/react-native#59722 ·
Maintainer antworten meist innerhalb von 2 Tagen
Alle Issues in react/react-native
Ähnliche Issues
-
crash generated by fuzzer mlir
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
llvm/llvm-project#243218 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
petercorke/robotics-toolbox-python#943 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
realtime
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 69/100
NVIDIA/cuda-quantum#5913 ·
Maintainer antworten meist innerhalb von 1 Tag
-
category:port-update
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
Maintainer antworten meist innerhalb von 2 Tagen
-
area:build bug
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 90/100
NatronGitHub/openfx-arena#71 ·
Maintainer antworten meist innerhalb von 1 Tag