[Reanimated] EXC_BAD_ACCESS: Exception 1, Code 1, Subcode 167039574753352 >

[sentry]

Sentry Issue: JETPACK-IOS-FHE

EXC_BAD_ACCESS: Exception 1, Code 1, Subcode 167039574753352 >
KERN_INVALID_ADDRESS at 0x97ebee844048.
  File "Scheduler.h", line 20, in reanimated::Queue<T>::~Queue
  File "Scheduler.h", line 20, in reanimated::Queue<T>::~Queue
  File "Scheduler.cpp", line 31, in reanimated::Scheduler::~Scheduler
  File "REAIOSErrorHandler.h", line 18, in reanimated::REAIOSErrorHandler::~REAIOSErrorHandler
  File "REAIOSErrorHandler.h", line 18, in reanimated::REAIOSErrorHandler::~REAIOSErrorHandler
...
(74 additional frame(s) were not displayed)

By July 3rd, 2023, this issue has impacted 59 users. The stack trace references the Reanimated library, which is only used in the editor.

[fluiddot]

This issue is likely to be related to #20499.

[wargcm]

Do we want to link JETPACK-IOS-FR9 to this as well? The stack trace is different but it's also a Reanimated crash.

JETPACK-IOS-F8R / WORDPRESS-IOS-3P8M also have Reanimated in the stack trace.

[fluiddot]

Do we want to link JETPACK-IOS-FR9 to this as well? The stack trace is different but it's also a Reanimated crash.

I checked a couple of events and noticed that one of the last actions was pressing the More button. This differs from this issue which seems it's mostly happening when closing the editor. Hence, although it's associated with Reanimated, I'd try to track it in a separate GitHub issue if possible.

JETPACK-IOS-F8R / WORDPRESS-IOS-3P8M also have Reanimated in the stack trace.

We have this issue that contains a very similar stack trace and title, probably we could associate them with it.

[dcalhoun]

Unfortunately, I believe I just encountered this crash running 22.9 with the latest React Native upgrade (#20956). 😞

[dcalhoun]

Ignore my previous comment. 22.9 does not include the latest React Native upgrade. 😅

[fluiddot]

Version 23.0, which includes the React Native upgrade, has been released already for a week and no events have been reported 🎊. Hence we can consider the crash solved.