Codegen leaves one folder per library in $TMPDIR on every pod install and Xcode build: generateCode never removes its mkdtempSync folder
Mantenedores costumam responder em até 2 dias
Avaliação
- Dificuldade
- 2/5
- Tempo estimado
- 1-3 horas
- Facilidade para iniciantes
- 35/100
- Tipo de issue
- Bug
- Clareza
- Claramente especificada
- Status de atividade
- Estagnada
- Stack de tecnologia
- javascript, node.js, react-native
- Domínio
- build-system, mobile
Direção de pesquisa
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.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
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
- Linguagem predominante
- C++
- Estrelas
- 127k
- Forks
- 25.5k
- Merge médio
- 3d 22h
- PRs com merge (30d)
- 235
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Tem um modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de react/react-native
-
Needs: Author Feedback Needs: Repro
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 82/100
react/react-native#60059 · 1 comentário ·
Mantenedores costumam responder em até 2 dias
-
Needs: Triage :mag:
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 70/100
react/react-native#60000 ·
Mantenedores costumam responder em até 2 dias
-
`yarn test-ios` exits before building RNTester: `objc-test.sh` launches the WebSocket server script #59433 deletedTalvez já em andamento @lazerg assumiu há 4 dias. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
react/react-native#59939 ·
Mantenedores costumam responder em até 2 dias
-
iOS Fabric pointer-handler reset leaves the next lone touch non-primaryTalvez já em andamento @alleneubank assumiu há 6 dias. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
react/react-native#59919 ·
Mantenedores costumam responder em até 2 dias
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 70/100
react/react-native#59722 ·
Mantenedores costumam responder em até 2 dias
Todas as issues de react/react-native
Issues semelhantes
-
bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
petercorke/robotics-toolbox-python#943 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
area:build bug
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 90/100
NatronGitHub/openfx-arena#71 ·
Mantenedores costumam responder em até 1 dia
-
upstream-watcher: Netflix/vmaf cf677baaa039 is not portedTalvez já em andamento Um pull request vinculado a esta issue está aberto ou já foi mesclado. Abertaupstream-blocked
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 65/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
ROCm/FastFlowLM#1057 ·
Mantenedores costumam responder em até 1 dia
-
bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
NatronGitHub/openfx-gmic#45 ·
Mantenedores costumam responder em até 1 dia