High memory usage for `Text` component on iOS
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- C++
- Sterne
- 127k
- Forks
- 25.3k
- Ø Merge
- 1 T. 23 Std.
- Gemergte PRs (30 T.)
- 4
Beschreibung
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.
This can be observed using Allocations Xcode Instrument by marking memory before and after adding text views.
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 haveCALayersattached
Steps to reproduce
- Download the reproducer app
yarn install&yarn ios:releaseORyarn android:release- Run the app on a simulator or a device
- Attach Allocation Xcode Instrument, mark generation A
- Pick "Text (Large Font)" from the component dropdown
- Press "Create Views"
- Wait a couple of seconds, mark generation B in instruments
- 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
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Reproduziere das Problem mit der verknüpften rn-memory-footprint-App mithilfe der Komponente “Text (Large Font)” und des Xcode Allocations Instrument. Beginne damit, RCTParagraphTextView und seinen zugrunde liegenden CALayer nachzuverfolgen, und vergleiche anschließend das beobachtete iOS-Verhalten mit dem nativen UILabel und Android; abgeschlossen ist die Aufgabe, wenn der übermäßige Speicherverbrauch pro View behoben ist, ohne das Verhalten von Text zu ändern.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- ios, react-native
- Bereich
- mobile, performance
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Ruhig
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 45/100