7b7c9f2309
Summary: We're seeing that GCs caused by memory warnings on Android are barely collecting any memory and are operating on much smaller heaps than natural GCs. This is likely due to some of the TRIM_MEMORY_* events firing too often. Log which event name it was, instead of the generic "memory warning", to narrow down the cases where the memory warning was helpful. Unhelpful warnings will later be moved to not force a GC. Note that this diff changes Venice, but we don't see any Venice heaps in production, so it won't matter much other than making the code match up. Also note that iOS has a similar memory warning in `RCTCxxBridge.mm`, but it hasn't been called in production. Perhaps iOS is less trigger-happy for memory warnings than Android. Changelog: [Internal] Reviewed By: neildhar Differential Revision: D24093394 fbshipit-source-id: 03304f0f79083133c4d9b730559aef291319b6eb |
||
|---|---|---|
| .. | ||
| jsireact | ||
| .clang-tidy | ||
| Android.mk | ||
| BUCK | ||
| React-jsiexecutor.podspec | ||