-
Notifications
You must be signed in to change notification settings - Fork 24.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iOS: Measure startup memory footprint #28215
Conversation
RNTester.app (iOS): 10678272 bytes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@shergin is landing this pull request. If you are a Facebook employee, you can view this diff on Phabricator.
This is currently blocked internally because of these failing unit tests:
Sample error console output:
|
This PR is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
Summary
As part of React Native Benchmark Suite, we are looking to surface the impact of a change on the memory footprint.
I hit an issue with the JavaScriptCore instance seemingly not being cleaned up properly, and somehow gets reused (see example output below). I haven't been able figure out what the deal is, but I think it might be valuable to check this in as is.
Changelog
[Internal] [Added] - Added initial memory footprint test (this will always pass for now)
Test Plan
This currently only outputs to the console: