[Crash] Unhandled: abort

[sentry-io[bot]]

Sentry Issue: JETPACK-ANDROID-8F9

SIGABRT: Abort
  ?, in abort
  ?, in art::Runtime::Abort
  ?
  ?, in __android_log_assert
  ?
...
(16 additional frame(s) were not displayed)

[SiobhyB]

Marking this crash as low priority as it was first introduced two months ago, in 22.5, and has impacted 29 users so far. @fluiddot, Sentry shows that you experienced this crash on August 30th, too. I wonder if it might be a dupe of another crash you've been investigating. Does anything about it seem at all familiar?

[fluiddot]

@fluiddot, Sentry shows that you experienced this crash on August 30th, too. I wonder if it might be a dupe of another crash you've been investigating. Does anything about it seem at all familiar?

Yes, I experienced it while investigating another crash. As far as I recall, I reproduced it on Android by following these steps:

1. Create a really long post by copying the HTML from https://automattic.com/how-we-work/ several times.
2. Enable the Android development option "Apps/Don't keep activities". This can be found in the Developer options screen within the device. NOTE: I think this was actually the main factor in reproducing the crash.
3. Open the post.
4. Scroll through the content and tap on some blocks.
5. Put the app in the background and resume it. This forces the editor's activity recreation when the above-mentioned developer option is enabled.
6. Repeat steps 4 and 5 several times until the app crashes.

I'd like to note that I couldn't reproduce it easily, in fact, after several times testing, I only managed to crash the app once. My gut feeling is that this might be more prone to happen on low-end devices, which might recreate the editor activity due to memory pressure.