react / react/react-native

High memory usage for `Text` component on iOS

Aperta
#54,847 1 commento 2 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Needs: Triage :mag: Platform: iOS
Lingua principale
C++
Stelle
127k
Fork
25.3k
Merge medio
1g 23h
PR unite (30g)
4

Descrizione

Description

When working on memory optimisation of a complex RN app, I found that Text components on iOS can consume relatively large amounts of memory. When I've checked that with Xcode Instruments, it seems that each RCTParagraphTextView is accompanied by a backing CALayer which consumes memory proportional to its rendered size, more precisely width x height x 4 bytes (RGBA channels).

While individual Text instances are small, complex UI, esp. using stacked screens & virtualized lists can add up to quite large number (tens of MB), especially if the app uses large font sizes in such lists.

For example, each of the following Text components consumes about 112-140 KB of memory, due to the backing raster.

Image

This can be observed using Allocations Xcode Instrument by marking memory before and after adding text views.

Image

I've created a small app for easily measuring various components' memory usage: https://github.com/mdjastrzebski/rn-memory-footprint

Note:

  • on Android, this issue does not seem to happen, as all Text have similar size, regardless of used font size
  • on iOS, when using native UILabel, these are much smaller, and do not have CALayers attached
Steps to reproduce
  1. Download the reproducer app
  2. yarn install & yarn ios:release OR yarn android:release
  3. Run the app on a simulator or a device
  4. Attach Allocation Xcode Instrument, mark generation A
  5. Pick "Text (Large Font)" from the component dropdown
  6. Press "Create Views"
  7. Wait a couple of seconds, mark generation B in instruments
  8. Compare memory usage. You should see a lot of RCTParagraphTextView (CALayer) entries, each taking 120-140 KBs.
React Native Version

0.82.1

Affected Platforms

Runtime - iOS

Output of npx @react-native-community/cli info
System:
  OS: macOS 26.1
  CPU: (11) arm64 Apple M3 Pro
  Memory: 102.75 MB / 36.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 22.17.1
    path: /Users/mdj/.nvm/versions/node/v22.17.1/bin/node
  Yarn:
    version: 4.12.0
    path: /Users/mdj/.nvm/versions/node/v22.17.1/bin/yarn
  npm:
    version: 10.9.2
    path: /Users/mdj/.nvm/versions/node/v22.17.1/bin/npm
  Watchman:
    version: 2025.07.28.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.16.2
    path: /Users/mdj/.rbenv/shims/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 25.0
      - iOS 26.0
      - macOS 26.0
      - tvOS 26.0
      - visionOS 26.0
      - watchOS 26.0
  Android SDK:
    API Levels:
      - "35"
      - "36"
    Build Tools:
      - 35.0.0
      - 36.0.0
    System Images:
      - android-35 | Google Play ARM 64 v8a
      - android-36 | Google Play ARM 64 v8a
    Android NDK: Not Found
IDEs:
  Android Studio: 2025.2 AI-252.25557.131.2521.14432022
  Xcode:
    version: 26.0.1/17A400
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.16
    path: /usr/bin/javac
  Ruby:
    version: 3.4.5
    path: /Users/mdj/.rbenv/shims/ruby
npmPackages:
  "@react-native-community/cli":
    installed: 20.0.0
    wanted: 20.0.0
  react:
    installed: 19.1.1
    wanted: 19.1.1
  react-native:
    installed: 0.82.1
    wanted: 0.82.1
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: true
iOS:
  hermesEnabled: true
  newArchEnabled: true
Stacktrace or Logs
n/a
MANDATORY Reproducer

https://github.com/mdjastrzebski/rn-memory-footprint

Screenshots and Videos

Added above

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Direzione di ricerca

Riproduci il problema con l’app rn-memory-footprint collegata usando il componente “Text (Large Font)” e Xcode Allocations Instrument. Inizia tracciando RCTParagraphTextView e il relativo CALayer sottostante, quindi confronta il comportamento osservato su iOS con UILabel nativo e Android; il lavoro è completo quando l’uso eccessivo di memoria per vista è stato risolto senza modificare il comportamento di Text.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
ios, react-native
Ambito
mobile, performance
Tipo di issue
Bug
Difficoltà
4/5
Tempo stimato
3-5 giorni
Stato di attività
Tranquilla
Chiarezza
Abbastanza chiara
Idoneità per principianti
45/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.