mirror of
https://github.com/facebook/react-native.git
synced 2025-11-01 09:14:26 +00:00
Joshua Gross
d5076c6c8f
Summary: There are a few places where we have JNI table ref leaks, and more places where we can aggressively clean up smart pointers immediately instead of waiting for them to be cleaned up at some later point. In theory these smart pointers should be cleaned up immediately, but in cases where many components are being measured at once, the JNI table could grow until all measure calls are done. In extreme cases this could cause a crash, which I want to avoid. At the very least, freeing memory more aggressively in this case can't hurt. Changelog: [Internal] Reviewed By: shergin Differential Revision: D24293775 fbshipit-source-id: 159741ba955e5a6fe02caf6e65d1e4d6d4afadee