Add exponential backoff to InspectorPackagerConnection reconnect and exception handling to connect (#56650)

[shubhamksavita]

Summary:

Summary

Fix occasional SIGSEGV in operator new during InspectorPackagerConnection::connectWebSocket().

Root Cause

The InspectorPackagerConnection reconnection loop retries every 2 seconds with no backoff or limit. When no Metro dev server is reachable, this results in hundreds of failed WebSocket connection attempts over the app lifetime. Each attempt allocates and deallocates C++ hybrid objects, JNI references, and OkHttp WebSocket instances. This accumulated churn leads to heap fragmentation and eventual heap metadata corruption, manifesting as SIGSEGV in operator new when the allocator follows corrupted internal pointers.

Additionally, the connect() method had no exception handling around the connectWebSocket() call, meaning any JNI/Java exception would propagate uncaught.

Changes

1. Exponential backoff in reconnect(): Start at 2s, double each retry, cap at 120s. This reduces reconnection attempts from ~500 in 17 minutes to ~15, drastically reducing resource churn.
2. Try-catch in connect(): Catch exceptions from connectWebSocket() (e.g., fbjni/JNI exceptions) and gracefully trigger a reconnect instead of crashing.
3. Reset backoff on success: When didOpen() fires (successful connection), reset the delay back to 2s and clear suppressConnectionErrors_.

Changelog:

[General][Fixed] - Add exponential backoff and exception handling to InspectorPackagerConnection reconnect loop to prevent heap fragmentation crashes

Reviewed By: cipolleschi

Differential Revision: D100956687

[meta-codesync]

@shubhamksavita has exported this pull request. If you are a Meta employee, you can view the originating Diff in D100956687.

[meta-codesync]

This pull request has been merged in 32d3eaf.

[react-native-bot]

This pull request was successfully merged by @shubhamksavita in 32d3eaf

^{When will my fix make it into a release? | How to file a pick request?}