Crash when opening and closing the editor: C++ Exception: NSt3__112system_errorE

[guarani]

Sentry issues:

• JETPACK-IOS-4A
• WORDPRESS-IOS-3KSC

Reference: Sentry search for NSt3__112system_errorE across both the JP and WP apps.

Potential solution

The crash should be addressed with #20956. More context.

Reproduction Steps

Copied from #20499 (comment).

1. Navigate to the post list screen.
2. Focus the search input and query for several posts.
3. Keep the search input focused.¹
4. Open and close a post.
5. Repeat step 4 until the app crashes.²

Footnotes

1. May not be necessary, but keyboard show/hide event are in numerous Sentry crash logs. ↩

2. Crashing occurs very infrequently. ↩

[guarani]

This might be related to React Native because it appears in the Stack Trace I downloaded from Sentry, e.g.:

Thread 9 name: com.facebook.react.JavaScript
0   libsystem_kernel.dylib          0x3aef6567c         __psynch_cvwait
1   libsystem_pthread.dylib         0x3cfe34068         _pthread_cond_wait
2   JavaScriptCore                  0x35a738ce8         WTF::ParkingLot::parkConditionallyImpl
3   JavaScriptCore                  0x35a6f9638         WTF::Condition::waitUntilUnchecked<T>
4   JavaScriptCore                  0x35b177188         JSC::Heap::lastChanceToFinalize
5   JavaScriptCore                  0x35b7f8608         JSC::VM::~VM
6   JavaScriptCore                  0x35b68a068         JSC::JSLockHolder::~JSLockHolder
7   JavaScriptCore                  0x35ab857e4         JSGlobalContextRelease
8   WordPress                       0x2042d69c0         facebook::jsc::JSCRuntime::~JSCRuntime (JSCRuntime.cpp:392)
9   WordPress                       0x2042d6ac0         [inlined] facebook::jsc::JSCRuntime::~JSCRuntime (JSCRuntime.cpp:384)
10  WordPress                       0x2042d6ac0         facebook::jsc::JSCRuntime::~JSCRuntime (JSCRuntime.cpp:384)
11  WordPress                       0x203ca7bd0         [inlined] std::__1::__shared_count::__release_shared (shared_ptr.h:177)
12  WordPress                       0x203ca7bd0         [inlined] std::__1::__shared_weak_count::__release_shared (shared_ptr.h:219)
13  WordPress                       0x203ca7bd0         std::__1::shared_ptr<T>::~shared_ptr (shared_ptr.h:959)
14  WordPress                       0x203ed5128         [inlined] std::__1::shared_ptr<T>::~shared_ptr (shared_ptr.h:957)
15  WordPress                       0x203ed5128         reanimated::RuntimeManager::~RuntimeManager (RuntimeManager.h:36)
16  WordPress                       0x203ed7168         reanimated::NativeReanimatedModule::~NativeReanimatedModule (NativeReanimatedModule.h:26)
17  WordPress                       0x203ca7bd0         [inlined] std::__1::__shared_count::__release_shared (shared_ptr.h:177)
18  WordPress                       0x203ca7bd0         [inlined] std::__1::__shared_weak_count::__release_shared (shared_ptr.h:219)
19  WordPress                       0x203ca7bd0         std::__1::shared_ptr<T>::~shared_ptr (shared_ptr.h:959)
20  WordPress                       0x2042d9320         [inlined] std::__1::shared_ptr<T>::~shared_ptr (shared_ptr.h:957)
21  WordPress                       0x2042d9320         [inlined] facebook::jsc::detail::HostObjectProxyBase::~HostObjectProxyBase (JSCRuntime.cpp:703)
22  WordPress                       0x2042d9320         [inlined] facebook::jsc::JSCRuntime::createObject::HostObjectProxy::~HostObjectProxy (JSCRuntime.cpp:720)
23  WordPress                       0x2042d9320         [inlined] facebook::jsc::JSCRuntime::createObject::HostObjectProxy::~HostObjectProxy (JSCRuntime.cpp:720)
24  WordPress                       0x2042d9320         facebook::jsc::JSCRuntime::createObject::HostObjectProxy::finalize (JSCRuntime.cpp:825)

[guarani]

👋 @geriux, do you have any context on this crash? I saw your name in the Activity tab of the Sentry issue for this crash. I bumped into this on Snetry during my release rotation because it's the top crash in 22.0, so I created this GitHub issue to help triage.

[geriux]

👋 @geriux, do you have any context on this crash? I saw your name in the Activity tab of the Sentry issue for this crash. I bumped into this on Snetry during my release rotation because it's the top crash in 22.0, so I created this GitHub issue to help triage.

It looks like it is related to this issue WordPress/gutenberg#41686 and the Reanimated library. After some investigations, we couldn't find a quick solution but we had some ideas like starting using Hermes on iOS or updating the Reanimated library to the latest version. I think we should revisit this as it is one of the top issues.

[guarani]

Thanks for the context, @geriux!

[guarani]

As for next steps, should someone be assigned to this issue? I should remove the Needs Triage label once it has an assignee (see internal ref PCYsg-vRg-p2).

[geriux]

Maybe we should add it to the Maintenance Week board?

[guarani]

Good idea!
@tiagomar I understand that you're maintaining the maintenance board (see React Native board). Would this be a good candidate as @geriux suggested above?

[guarani]

I assessed this as priority due to Medium severity (assuming drag & drop is a low priority feature) and Medium impact (unsure about it, but maybe 6-24% of users affected given the 101 events in last 24 hours).

[guarani]

Do you think https://a8c.sentry.io/issues/3322079168 is a duplicate of the Sentry issue mentioned at the top of this issue, @geriux? I found them to have the same error, C++ Exception NSt3__112system_errorE but when viewing either of them, I couldn't get Sentry to list the other under the Similar Issues in order to merge them.