Scrolling to the end of a post containing an Embed block crashes the Android native editor

[dcalhoun]

Description

When a long post contains an Embed block (e.g. Twitter, YouTube), the native editor will crash after scrolling to the end of the post.

Step-by-step reproduction instructions

1. Create a new post within the Android native editor.
2. Copy a Twitter URL to your clipboard. (Note: It cannot be a mobile Twitter URL.)
3. Add a Twitter block¹.
4. Dismissing the block settings bottom sheet to persist the Twitter URL for the block.
5. Repeat steps 2-4 a few more times so that there enough content to scroll the first/last block out of view.
6. Scroll the post content to the end causing the scrolling to cease.

¹ Twitter block is one example, but the same outcome can occur for YouTube and other embeds.

Expected behaviour

The editor does not crash.

Actual behaviour

The editor crashes.

Android Studio error logs

2022-07-18 14:57:45.103 2061-2346/org.wordpress.android.prealpha A/libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x20 in tid 2346 (RenderThread), pid 2061 (ndroid.prealpha)
2022-07-18 14:57:46.285 6630-6630/? E/USNET: USNET: appName: org.wordpress.android.prealpha
2022-07-18 14:57:46.675 6630-6709/org.wordpress.android.prealpha E/chromium: [ERROR:simple_file_enumerator.cc(21)] opendir /data/user/0/org.wordpress.android.prealpha/cache/webview_org.wordpress.android.prealpha/Default/HTTP Cache/Code Cache/js: No such file or directory (2)
2022-07-18 14:57:46.675 6630-6709/org.wordpress.android.prealpha E/chromium: [ERROR:simple_index_file.cc(617)] Could not reconstruct index from disk

Screenshots or screen recording (optional)

Screen_Recording_20220718-151526_WordPress.mp4

WordPress information

• WordPress version: 6.0
• Gutenberg version: 13.6.0
• Are all plugins except Gutenberg deactivated? Yes
• Are you using a default theme (e.g. Twenty Twenty-One)? Geologist

Device information

• Device: Samsung Galaxy S20
• Operating system: Android 12
• WordPress app version: WP 20.2

[fluiddot]

I think this might be also related to this issue, as on Sentry, the crash is reported as Segfault (reference). Besides the crash is affecting 95% of Android 12 users which is aligned with the fix description that states that only affects the Android 12 version.