Also: this is using the arm64 apk

Update: Tested on Galaxy Tab S8 Plus, and the crashes happen there too.

Can you provide the crash log from 'Help->Show crash log for bug reports.'?

For what it's worth, I've yet to experience any crashes with 5.2.0-beta1 on my ARM32 Android device, while transforming or otherwise.

Yeah. Here are the last two crashes on my Tab S8+, 64 bit:

********************** Dumping backtrace **********************
Signal: 11 (SIGSEGV) (Code: 1) Time: Thu Jul 27 21:45:49 2023 GMT Version: 5.2.0-beta1
  #00 pc 00000000003f4918  /data/app/~~V8d3VPDg02GwuLCqnowMog==/org.krita-KQdq6mC5MQeH0RfkYQ8guQ==/lib/arm64/libQt5Core_arm64-v8a.so (QCoreApplication::notifyInternal2(QObject*, QEvent*)+140)
  #01 pc 000000000042c474  /data/app/~~V8d3VPDg02GwuLCqnowMog==/org.krita-KQdq6mC5MQeH0RfkYQ8guQ==/lib/arm64/libQt5Core_arm64-v8a.so (QTimerInfoList::activateTimers()+572)
  #02 pc 000000000042ab44  /data/app/~~V8d3VPDg02GwuLCqnowMog==/org.krita-KQdq6mC5MQeH0RfkYQ8guQ==/lib/arm64/libQt5Core_arm64-v8a.so (QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)+424)
  #03 pc 000000000007f804  /data/app/~~V8d3VPDg02GwuLCqnowMog==/org.krita-KQdq6mC5MQeH0RfkYQ8guQ==/lib/arm64/libplugins_platforms_qtforandroid_arm64-v8a.so

********************** Dumping backtrace **********************
Signal: 11 (SIGSEGV) (Code: 1) Time: Thu Jul 27 21:49:09 2023 GMT Version: 5.2.0-beta1
  #00 pc 00000000003f4918  /data/app/~~V8d3VPDg02GwuLCqnowMog==/org.krita-KQdq6mC5MQeH0RfkYQ8guQ==/lib/arm64/libQt5Core_arm64-v8a.so (QCoreApplication::notifyInternal2(QObject*, QEvent*)+140)
  #01 pc 000000000042c474  /data/app/~~V8d3VPDg02GwuLCqnowMog==/org.krita-KQdq6mC5MQeH0RfkYQ8guQ==/lib/arm64/libQt5Core_arm64-v8a.so (QTimerInfoList::activateTimers()+572)
  #02 pc 000000000042ab44  /data/app/~~V8d3VPDg02GwuLCqnowMog==/org.krita-KQdq6mC5MQeH0RfkYQ8guQ==/lib/arm64/libQt5Core_arm64-v8a.so (QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)+424)
  #03 pc 000000000007f804  /data/app/~~V8d3VPDg02GwuLCqnowMog==/org.krita-KQdq6mC5MQeH0RfkYQ8guQ==/lib/arm64/libplugins_platforms_qtforandroid_arm64-v8a.so

Here's another crash:

********************** Dumping backtrace **********************
Signal: 11 (SIGSEGV) (Code: 1) Time: Thu Jul 27 22:04:08 2023 GMT Version: 5.2.0-beta1
  #00 pc 00000000003f4914  /data/app/~~V8d3VPDg02GwuLCqnowMog==/org.krita-KQdq6mC5MQeH0RfkYQ8guQ==/lib/arm64/libQt5Core_arm64-v8a.so (QCoreApplication::notifyInternal2(QObject*, QEvent*)+136)
  #01 pc 000000000042c474  /data/app/~~V8d3VPDg02GwuLCqnowMog==/org.krita-KQdq6mC5MQeH0RfkYQ8guQ==/lib/arm64/libQt5Core_arm64-v8a.so (QTimerInfoList::activateTimers()+572)
  #02 pc 000000000042ab44  /data/app/~~V8d3VPDg02GwuLCqnowMog==/org.krita-KQdq6mC5MQeH0RfkYQ8guQ==/lib/arm64/libQt5Core_arm64-v8a.so (QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)+424)
  #03 pc 000000000007f804  /data/app/~~V8d3VPDg02GwuLCqnowMog==/org.krita-KQdq6mC5MQeH0RfkYQ8guQ==/lib/arm64/libplugins_platforms_qtforandroid_arm64-v8a.so

Just to add to this, I have a Galaxy Tab S7+ and the crash has been recurring this whole year based on nightly build.

The easy way to replicate crash is to create a group of layers and select one layer.

However, i got curious and installed the beta on Xiaomi 11T pro and it has not crashed yet.

This makes me believe it is more of Samsung specific error (maybe s-pen issue or GPU driver bug). Both devices are running android 13
,

Doesn't look like driver issue because the crash is here even without hardware acceleration enabled

*** Bug 472993 has been marked as a duplicate of this bug. ***

Confirming based on multiple reports and the crash log. Unfortunately the crashlog isn't very helpful in this case (it's just somewhere in the event loop).

> the crash has been recurring this whole year based on nightly build.
Do you happen to know exactly when it started crashing? That could help narrow down the cause.

Other than that, it may take some detailed debugging by someone who can reproduce to figure it out.

Hi Freya, tough to say when it incurred cuz i didn't saved the last nightly that worked. A large window if this help is that it started before merging of neq qt. And after that check box for layer selection was added. Not sure if this helps. Layer selection was working wonderfully

Created attachment 161083 [details]
attachment-2299520-0.html

Hi. My name is Steven. I use a Galaxy Tab S8 Plus, I can screen record my
Krita crashing and I can run you through from setup to crashing and show
you each instance within an hour video. Would you like me to go ahead and
do that for you? I can have it to you quickly and promptly the moment you
send me a reply to this email and just let me know where you would like me
to upload it to so that the nightly Bill Developers may be able to correct
this problem as I love working in Krita but this crashing is just
ridiculous, lol. :-)

On Sun, Aug 20, 2023, 8:41 AM <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=472705
>
> --- Comment #10 from abhifx@gmail.com ---
> Hi Freya, tough to say when it incurred cuz i didn't saved the last nightly
> that worked. A large window if this help is that it started before merging
> of
> neq qt. And after that check box for layer selection was added. Not sure if
> this helps. Layer selection was working wonderfully
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.

================================================================================
SESSION: 02 Sep 2023 10:08:23 +0100. Executing /data/app/~~EXaVK6iK281yV29p-fTB0A==/org.krita.next-HnP8v2GoIpxUyfMa2sjgHw==/lib/arm64/libkrita_arm64-v8a.so

Krita Version: 5.3.0-prealpha (git 27c35ad), Qt version compiled: 5.15.7, loaded: 5.15.7. Process ID: 21371
-- -- -- -- -- -- -- --
02 Sep 2023 10:08:23 +0100: Style: fusion. Available styles: android, Windows, Fusion
02 Sep 2023 10:08:23 +0100: Creating database from scratch (database didn't exist, new schema version: 0.0.17).
02 Sep 2023 10:08:55 +0100: Created image "Unnamed", 2480 * 3508 pixels, 300 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 2
02 Sep 2023 10:15:55 +0100: Autosaving: /storage/emulated/0/Android/data/org.krita.next/files/Documents/krita-backup/krita-21371-document_0-autosave.kra
02 Sep 2023 10:15:55 +0100: Converting from application/x-krita to application/x-krita. Location: /storage/emulated/0/Android/data/org.krita.next/files/Documents/krita-backup/krita-21371-document_0-autosave.kra. Real location: /storage/emulated/0/Android/data/org.krita.next/files/Documents/krita-backup/krita-21371-document_0-autosave.kra. Batchmode: 0. Configuration: none
02 Sep 2023 10:15:55 +0100: Completed saving /storage/emulated/0/Android/data/org.krita.next/files/Documents/krita-backup/krita-21371-document_0-autosave.kra (mime: application/x-krita). Result: OK. Warning: . Size: 737405
02 Sep 2023 10:23:02 +0100: Autosaving: /storage/emulated/0/Android/data/org.krita.next/files/Documents/krita-backup/krita-21371-document_0-autosave.kra
02 Sep 2023 10:23:12 +0100: Autosaving: /storage/emulated/0/Android/data/org.krita.next/files/Documents/krita-backup/krita-21371-document_0-autosave.kra
02 Sep 2023 10:23:14 +0100: SAFE ASSERT (krita): "!m_d->readyShortcut" in file /home/user/workspace/Krita_Nightly_Android_arm64-v8a_Build/krita/libs/ui/input/kis_shortcut_matcher.cpp, line 820

KRITA DID NOT CLOSE CORRECTLY
================================================================================
SESSION: 02 Sep 2023 10:24:39 +0100. Executing /data/app/~~EXaVK6iK281yV29p-fTB0A==/org.krita.next-HnP8v2GoIpxUyfMa2sjgHw==/lib/arm64/libkrita_arm64-v8a.so

Krita Version: 5.3.0-prealpha (git 27c35ad), Qt version compiled: 5.15.7, loaded: 5.15.7. Process ID: 24240
-- -- -- -- -- -- -- --
02 Sep 2023 10:24:39 +0100: Style: fusion. Available styles: android, Windows, Fusion
02 Sep 2023 10:24:39 +0100: Database is up to date. Version: 0.0.17, created by Krita 5.3.0-prealpha, at Sat Sept 2 10:08:23 2023
02 Sep 2023 10:24:58 +0100: Created image "Unnamed", 2480 * 3508 pixels, 300 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 2
02 Sep 2023 10:25:19 +0100: SAFE ASSERT (krita): "!m_d->readyShortcut" in file /home/user/workspace/Krita_Nightly_Android_arm64-v8a_Build/krita/libs/ui/input/kis_shortcut_matcher.cpp, line 820
02 Sep 2023 10:26:14 +0100: SAFE ASSERT (krita): "result.isNull() || m_d->containsOriginal(key)" in file /home/user/workspace/Krita_Nightly_Android_arm64-v8a_Build/krita/libs/resources/KisResourceThumbnailCache.cpp, line 193
02 Sep 2023 10:26:23 +0100: SAFE ASSERT (krita): "result.isNull() || m_d->containsOriginal(key)" in file /home/user/workspace/Krita_Nightly_Android_arm64-v8a_Build/krita/libs/resources/KisResourceThumbnailCache.cpp, line 193
02 Sep 2023 10:26:54 +0100: SAFE ASSERT (krita): "!m_d->readyShortcut" in file /home/user/workspace/Krita_Nightly_Android_arm64-v8a_Build/krita/libs/ui/input/kis_shortcut_matcher.cpp, line 820

KRITA DID NOT CLOSE CORRECTLY
================================================================================
SESSION: 02 Sep 2023 10:27:56 +0100. Executing /data/app/~~EXaVK6iK281yV29p-fTB0A==/org.krita.next-HnP8v2GoIpxUyfMa2sjgHw==/lib/arm64/libkrita_arm64-v8a.so

Krita Version: 5.3.0-prealpha (git 27c35ad), Qt version compiled: 5.15.7, loaded: 5.15.7. Process ID: 24914
-- -- -- -- -- -- -- --
02 Sep 2023 10:27:56 +0100: Style: fusion. Available styles: android, Windows, Fusion
02 Sep 2023 10:27:56 +0100: Database is up to date. Version: 0.0.17, created by Krita 5.3.0-prealpha, at Sat Sept 2 10:08:23 2023
02 Sep 2023 10:28:10 +0100: Created image "Unnamed", 2480 * 3508 pixels, 300 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 2
02 Sep 2023 10:32:02 +0100: SAFE ASSERT (krita): "result.isNull() || m_d->containsOriginal(key)" in file /home/user/workspace/Krita_Nightly_Android_arm64-v8a_Build/krita/libs/resources/KisResourceThumbnailCache.cpp, line 193
02 Sep 2023 10:35:10 +0100: Autosaving: /storage/emulated/0/Android/data/org.krita.next/files/Documents/krita-backup/krita-24914-document_0-autosave.kra
02 Sep 2023 10:35:10 +0100: Converting from application/x-krita to application/x-krita. Location: /storage/emulated/0/Android/data/org.krita.next/files/Documents/krita-backup/krita-24914-document_0-autosave.kra. Real location: /storage/emulated/0/Android/data/org.krita.next/files/Documents/krita-backup/krita-24914-document_0-autosave.kra. Batchmode: 0. Configuration: none
02 Sep 2023 10:35:10 +0100: Completed saving /storage/emulated/0/Android/data/org.krita.next/files/Documents/krita-backup/krita-24914-document_0-autosave.kra (mime: application/x-krita). Result: OK. Warning: . Size: 4375315

KRITA DID NOT CLOSE CORRECTLY
================================================================================
SESSION: 02 Sep 2023 10:39:30 +0100. Executing /data/app/~~EXaVK6iK281yV29p-fTB0A==/org.krita.next-HnP8v2GoIpxUyfMa2sjgHw==/lib/arm64/libkrita_arm64-v8a.so

Krita Version: 5.3.0-prealpha (git 27c35ad), Qt version compiled: 5.15.7, loaded: 5.15.7. Process ID: 26953
-- -- -- -- -- -- -- --
02 Sep 2023 10:39:30 +0100: Style: fusion. Available styles: android, Windows, Fusion
02 Sep 2023 10:39:30 +0100: Database is up to date. Version: 0.0.17, created by Krita 5.3.0-prealpha, at Sat Sept 2 10:08:23 2023
02 Sep 2023 10:39:36 +0100: Removing autosave file /storage/emulated/0/Android/data/org.krita.next/files/Documents/krita-backup/krita-21371-document_0-autosave.kra
02 Sep 2023 10:39:36 +0100: Removing autosave file /storage/emulated/0/Android/data/org.krita.next/files/Documents/krita-backup/krita-24914-document_0-autosave.kra
02 Sep 2023 10:39:41 +0100: Created image "Unnamed", 2480 * 3508 pixels, 300 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 2

KRITA DID NOT CLOSE CORRECTLY
================================================================================
SESSION: 02 Sep 2023 10:39:57 +0100. Executing /data/app/~~EXaVK6iK281yV29p-fTB0A==/org.krita.next-HnP8v2GoIpxUyfMa2sjgHw==/lib/arm64/libkrita_arm64-v8a.so

Krita Version: 5.3.0-prealpha (git 27c35ad), Qt version compiled: 5.15.7, loaded: 5.15.7. Process ID: 27166
-- -- -- -- -- -- -- --
02 Sep 2023 10:39:57 +0100: Style: fusion. Available styles: android, Windows, Fusion
02 Sep 2023 10:39:57 +0100: Database is up to date. Version: 0.0.17, created by Krita 5.3.0-prealpha, at Sat Sept 2 10:08:23 2023

KRITA DID NOT CLOSE CORRECTLY
================================================================================
SESSION: 02 Sep 2023 10:41:51 +0100. Executing /data/app/~~EXaVK6iK281yV29p-fTB0A==/org.krita.next-HnP8v2GoIpxUyfMa2sjgHw==/lib/arm64/libkrita_arm64-v8a.so

Krita Version: 5.3.0-prealpha (git 27c35ad), Qt version compiled: 5.15.7, loaded: 5.15.7. Process ID: 29262
-- -- -- -- -- -- -- --
02 Sep 2023 10:41:51 +0100: Style: fusion. Available styles: android, Windows, Fusion
02 Sep 2023 10:41:52 +0100: Database is up to date. Version: 0.0.17, created by Krita 5.3.0-prealpha, at Sat Sept 2 10:08:23 2023
02 Sep 2023 10:42:21 +0100: Created image "Unnamed", 2480 * 3508 pixels, 300 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 2
02 Sep 2023 10:46:49 +0100: SAFE ASSERT (krita): "!m_d->readyShortcut" in file /home/user/workspace/Krita_Nightly_Android_arm64-v8a_Build/krita/libs/ui/input/kis_shortcut_matcher.cpp, line 847
Not sure if this helps - please let me know. Latest nightly build running on a Samsung S9 Ultra tablet. I tried to minimise demand on Android (no other apps running) no use of S pen (finger painting only). Default canvas size, two layers only, no Configuration changes other than Workspace. Crashes appeared to occur randomly (one possible pattern to follow). After one crash Android would not start KritaNext Android system gave a error message (roughly) stating a bug in Krita and wait for an update from developers. The only pattern I could see linking to the crashes was changing the Workspace via the Toolbar icon (far right hand side). Crashes didn't always occur when changing Workspace but three crashes did occur on changing Workspace.

KRITA DID NOT CLOSE CORRECTLY
================================================================================
SESSION: 02 Sep 2023 10:47:38 +0100. Executing /data/app/~~EXaVK6iK281yV29p-fTB0A==/org.krita.next-HnP8v2GoIpxUyfMa2sjgHw==/lib/arm64/libkrita_arm64-v8a.so

Krita Version: 5.3.0-prealpha (git 27c35ad), Qt version compiled: 5.15.7, loaded: 5.15.7. Process ID: 30453
-- -- -- -- -- -- -- --
02 Sep 2023 10:47:38 +0100: Style: fusion. Available styles: android, Windows, Fusion
02 Sep 2023 10:47:39 +0100: Database is up to date. Version: 0.0.17, created by Krita 5.3.0-prealpha, at Sat Sept 2 10:08:23 2023

Created attachment 161341 [details]
attachment-4104684-0.html

Please take me off the CC list. Since you guys haven't and aren't bothering
to fix the consistent crashes on the Samsung Tab S8 series, your emails are
just spam at this point.

On Sat, Sep 2, 2023, 3:12 AM Kevin Bell <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=472705
>
> Kevin Bell <kev.bell@sky.com> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|                            |kev.bell@sky.com
>
> --- Comment #12 from Kevin Bell <kev.bell@sky.com> ---
>
> ================================================================================
> SESSION: 02 Sep 2023 10:08:23 +0100. Executing
>
> /data/app/~~EXaVK6iK281yV29p-fTB0A==/org.krita.next-HnP8v2GoIpxUyfMa2sjgHw==/lib/arm64/libkrita_arm64-v8a.so
>
> Krita Version: 5.3.0-prealpha (git 27c35ad), Qt version compiled: 5.15.7,
> loaded: 5.15.7. Process ID: 21371
> -- -- -- -- -- -- -- --
> 02 Sep 2023 10:08:23 +0100: Style: fusion. Available styles: android,
> Windows,
> Fusion
> 02 Sep 2023 10:08:23 +0100: Creating database from scratch (database didn't
> exist, new schema version: 0.0.17).
> 02 Sep 2023 10:08:55 +0100: Created image "Unnamed", 2480 * 3508 pixels,
> 300
> dpi. Color model: 8-bit integer/channel RGB/Alpha
> (sRGB-elle-V2-srgbtrc.icc).
> Layers: 2
> 02 Sep 2023 10:15:55 +0100: Autosaving:
>
> /storage/emulated/0/Android/data/org.krita.next/files/Documents/krita-backup/krita-21371-document_0-autosave.kra
> 02 Sep 2023 10:15:55 +0100: Converting from application/x-krita to
> application/x-krita. Location:
>
> /storage/emulated/0/Android/data/org.krita.next/files/Documents/krita-backup/krita-21371-document_0-autosave.kra.
> Real location:
>
> /storage/emulated/0/Android/data/org.krita.next/files/Documents/krita-backup/krita-21371-document_0-autosave.kra.
> Batchmode: 0. Configuration: none
> 02 Sep 2023 10:15:55 +0100: Completed saving
>
> /storage/emulated/0/Android/data/org.krita.next/files/Documents/krita-backup/krita-21371-document_0-autosave.kra
> (mime: application/x-krita). Result: OK. Warning: . Size: 737405
> 02 Sep 2023 10:23:02 +0100: Autosaving:
>
> /storage/emulated/0/Android/data/org.krita.next/files/Documents/krita-backup/krita-21371-document_0-autosave.kra
> 02 Sep 2023 10:23:12 +0100: Autosaving:
>
> /storage/emulated/0/Android/data/org.krita.next/files/Documents/krita-backup/krita-21371-document_0-autosave.kra
> 02 Sep 2023 10:23:14 +0100: SAFE ASSERT (krita): "!m_d->readyShortcut" in
> file
>
> /home/user/workspace/Krita_Nightly_Android_arm64-v8a_Build/krita/libs/ui/input/kis_shortcut_matcher.cpp,
> line 820
>
> KRITA DID NOT CLOSE CORRECTLY
>
> ================================================================================
> SESSION: 02 Sep 2023 10:24:39 +0100. Executing
>
> /data/app/~~EXaVK6iK281yV29p-fTB0A==/org.krita.next-HnP8v2GoIpxUyfMa2sjgHw==/lib/arm64/libkrita_arm64-v8a.so
>
> Krita Version: 5.3.0-prealpha (git 27c35ad), Qt version compiled: 5.15.7,
> loaded: 5.15.7. Process ID: 24240
> -- -- -- -- -- -- -- --
> 02 Sep 2023 10:24:39 +0100: Style: fusion. Available styles: android,
> Windows,
> Fusion
> 02 Sep 2023 10:24:39 +0100: Database is up to date. Version: 0.0.17,
> created by
> Krita 5.3.0-prealpha, at Sat Sept 2 10:08:23 2023
> 02 Sep 2023 10:24:58 +0100: Created image "Unnamed", 2480 * 3508 pixels,
> 300
> dpi. Color model: 8-bit integer/channel RGB/Alpha
> (sRGB-elle-V2-srgbtrc.icc).
> Layers: 2
> 02 Sep 2023 10:25:19 +0100: SAFE ASSERT (krita): "!m_d->readyShortcut" in
> file
>
> /home/user/workspace/Krita_Nightly_Android_arm64-v8a_Build/krita/libs/ui/input/kis_shortcut_matcher.cpp,
> line 820
> 02 Sep 2023 10:26:14 +0100: SAFE ASSERT (krita): "result.isNull() ||
> m_d->containsOriginal(key)" in file
>
> /home/user/workspace/Krita_Nightly_Android_arm64-v8a_Build/krita/libs/resources/KisResourceThumbnailCache.cpp,
> line 193
> 02 Sep 2023 10:26:23 +0100: SAFE ASSERT (krita): "result.isNull() ||
> m_d->containsOriginal(key)" in file
>
> /home/user/workspace/Krita_Nightly_Android_arm64-v8a_Build/krita/libs/resources/KisResourceThumbnailCache.cpp,
> line 193
> 02 Sep 2023 10:26:54 +0100: SAFE ASSERT (krita): "!m_d->readyShortcut" in
> file
>
> /home/user/workspace/Krita_Nightly_Android_arm64-v8a_Build/krita/libs/ui/input/kis_shortcut_matcher.cpp,
> line 820
>
> KRITA DID NOT CLOSE CORRECTLY
>
> ================================================================================
> SESSION: 02 Sep 2023 10:27:56 +0100. Executing
>
> /data/app/~~EXaVK6iK281yV29p-fTB0A==/org.krita.next-HnP8v2GoIpxUyfMa2sjgHw==/lib/arm64/libkrita_arm64-v8a.so
>
> Krita Version: 5.3.0-prealpha (git 27c35ad), Qt version compiled: 5.15.7,
> loaded: 5.15.7. Process ID: 24914
> -- -- -- -- -- -- -- --
> 02 Sep 2023 10:27:56 +0100: Style: fusion. Available styles: android,
> Windows,
> Fusion
> 02 Sep 2023 10:27:56 +0100: Database is up to date. Version: 0.0.17,
> created by
> Krita 5.3.0-prealpha, at Sat Sept 2 10:08:23 2023
> 02 Sep 2023 10:28:10 +0100: Created image "Unnamed", 2480 * 3508 pixels,
> 300
> dpi. Color model: 8-bit integer/channel RGB/Alpha
> (sRGB-elle-V2-srgbtrc.icc).
> Layers: 2
> 02 Sep 2023 10:32:02 +0100: SAFE ASSERT (krita): "result.isNull() ||
> m_d->containsOriginal(key)" in file
>
> /home/user/workspace/Krita_Nightly_Android_arm64-v8a_Build/krita/libs/resources/KisResourceThumbnailCache.cpp,
> line 193
> 02 Sep 2023 10:35:10 +0100: Autosaving:
>
> /storage/emulated/0/Android/data/org.krita.next/files/Documents/krita-backup/krita-24914-document_0-autosave.kra
> 02 Sep 2023 10:35:10 +0100: Converting from application/x-krita to
> application/x-krita. Location:
>
> /storage/emulated/0/Android/data/org.krita.next/files/Documents/krita-backup/krita-24914-document_0-autosave.kra.
> Real location:
>
> /storage/emulated/0/Android/data/org.krita.next/files/Documents/krita-backup/krita-24914-document_0-autosave.kra.
> Batchmode: 0. Configuration: none
> 02 Sep 2023 10:35:10 +0100: Completed saving
>
> /storage/emulated/0/Android/data/org.krita.next/files/Documents/krita-backup/krita-24914-document_0-autosave.kra
> (mime: application/x-krita). Result: OK. Warning: . Size: 4375315
>
> KRITA DID NOT CLOSE CORRECTLY
>
> ================================================================================
> SESSION: 02 Sep 2023 10:39:30 +0100. Executing
>
> /data/app/~~EXaVK6iK281yV29p-fTB0A==/org.krita.next-HnP8v2GoIpxUyfMa2sjgHw==/lib/arm64/libkrita_arm64-v8a.so
>
> Krita Version: 5.3.0-prealpha (git 27c35ad), Qt version compiled: 5.15.7,
> loaded: 5.15.7. Process ID: 26953
> -- -- -- -- -- -- -- --
> 02 Sep 2023 10:39:30 +0100: Style: fusion. Available styles: android,
> Windows,
> Fusion
> 02 Sep 2023 10:39:30 +0100: Database is up to date. Version: 0.0.17,
> created by
> Krita 5.3.0-prealpha, at Sat Sept 2 10:08:23 2023
> 02 Sep 2023 10:39:36 +0100: Removing autosave file
>
> /storage/emulated/0/Android/data/org.krita.next/files/Documents/krita-backup/krita-21371-document_0-autosave.kra
> 02 Sep 2023 10:39:36 +0100: Removing autosave file
>
> /storage/emulated/0/Android/data/org.krita.next/files/Documents/krita-backup/krita-24914-document_0-autosave.kra
> 02 Sep 2023 10:39:41 +0100: Created image "Unnamed", 2480 * 3508 pixels,
> 300
> dpi. Color model: 8-bit integer/channel RGB/Alpha
> (sRGB-elle-V2-srgbtrc.icc).
> Layers: 2
>
> KRITA DID NOT CLOSE CORRECTLY
>
> ================================================================================
> SESSION: 02 Sep 2023 10:39:57 +0100. Executing
>
> /data/app/~~EXaVK6iK281yV29p-fTB0A==/org.krita.next-HnP8v2GoIpxUyfMa2sjgHw==/lib/arm64/libkrita_arm64-v8a.so
>
> Krita Version: 5.3.0-prealpha (git 27c35ad), Qt version compiled: 5.15.7,
> loaded: 5.15.7. Process ID: 27166
> -- -- -- -- -- -- -- --
> 02 Sep 2023 10:39:57 +0100: Style: fusion. Available styles: android,
> Windows,
> Fusion
> 02 Sep 2023 10:39:57 +0100: Database is up to date. Version: 0.0.17,
> created by
> Krita 5.3.0-prealpha, at Sat Sept 2 10:08:23 2023
>
> KRITA DID NOT CLOSE CORRECTLY
>
> ================================================================================
> SESSION: 02 Sep 2023 10:41:51 +0100. Executing
>
> /data/app/~~EXaVK6iK281yV29p-fTB0A==/org.krita.next-HnP8v2GoIpxUyfMa2sjgHw==/lib/arm64/libkrita_arm64-v8a.so
>
> Krita Version: 5.3.0-prealpha (git 27c35ad), Qt version compiled: 5.15.7,
> loaded: 5.15.7. Process ID: 29262
> -- -- -- -- -- -- -- --
> 02 Sep 2023 10:41:51 +0100: Style: fusion. Available styles: android,
> Windows,
> Fusion
> 02 Sep 2023 10:41:52 +0100: Database is up to date. Version: 0.0.17,
> created by
> Krita 5.3.0-prealpha, at Sat Sept 2 10:08:23 2023
> 02 Sep 2023 10:42:21 +0100: Created image "Unnamed", 2480 * 3508 pixels,
> 300
> dpi. Color model: 8-bit integer/channel RGB/Alpha
> (sRGB-elle-V2-srgbtrc.icc).
> Layers: 2
> 02 Sep 2023 10:46:49 +0100: SAFE ASSERT (krita): "!m_d->readyShortcut" in
> file
>
> /home/user/workspace/Krita_Nightly_Android_arm64-v8a_Build/krita/libs/ui/input/kis_shortcut_matcher.cpp,
> line 847
> Not sure if this helps - please let me know. Latest nightly build running
> on a
> Samsung S9 Ultra tablet. I tried to minimise demand on Android (no other
> apps
> running) no use of S pen (finger painting only). Default canvas size, two
> layers only, no Configuration changes other than Workspace. Crashes
> appeared to
> occur randomly (one possible pattern to follow). After one crash Android
> would
> not start KritaNext Android system gave a error message (roughly) stating
> a bug
> in Krita and wait for an update from developers. The only pattern I could
> see
> linking to the crashes was changing the Workspace via the Toolbar icon (far
> right hand side). Crashes didn't always occur when changing Workspace but
> three
> crashes did occur on changing Workspace.
>
> KRITA DID NOT CLOSE CORRECTLY
>
> ================================================================================
> SESSION: 02 Sep 2023 10:47:38 +0100. Executing
>
> /data/app/~~EXaVK6iK281yV29p-fTB0A==/org.krita.next-HnP8v2GoIpxUyfMa2sjgHw==/lib/arm64/libkrita_arm64-v8a.so
>
> Krita Version: 5.3.0-prealpha (git 27c35ad), Qt version compiled: 5.15.7,
> loaded: 5.15.7. Process ID: 30453
> -- -- -- -- -- -- -- --
> 02 Sep 2023 10:47:38 +0100: Style: fusion. Available styles: android,
> Windows,
> Fusion
> 02 Sep 2023 10:47:39 +0100: Database is up to date. Version: 0.0.17,
> created by
> Krita 5.3.0-prealpha, at Sat Sept 2 10:08:23 2023
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.

Hi, Steven!

The bug is a release blocker for the upcoming Krita 5.2 release, so we **are** working on that. 

I will remove you from the CC-list. You can subscribe later if you like.

I haven't had luck in reproducing this bug for the longest of times. I remember it being reported multiple times.. I wish the crash logs were more helpful, can you please do a screen capture if possible, so I can see if there is anything in the user action which causes the crash that I'm not doing.

(In reply to sh_zam from comment #15)
> I haven't had luck in reproducing this bug for the longest of times. I
> remember it being reported multiple times.. I wish the crash logs were more
> helpful, can you please do a screen capture if possible, so I can see if
> there is anything in the user action which causes the crash that I'm not
> doing.

Hi Shazam, This is easy to replicate on samsung device. Just create two or more layers, group them and select one of the layers in group and it instantly crashes. 

this however is not replicated in my xiaomi device. not sure what is the issue

(In reply to abhifx from comment #16)
> (In reply to sh_zam from comment #15)
> > I haven't had luck in reproducing this bug for the longest of times. I
> > remember it being reported multiple times.. I wish the crash logs were more
> > helpful, can you please do a screen capture if possible, so I can see if
> > there is anything in the user action which causes the crash that I'm not
> > doing.
> 
> Hi Shazam, This is easy to replicate on samsung device. Just create two or
> more layers, group them and select one of the layers in group and it
> instantly crashes. 
> 
> this however is not replicated in my xiaomi device. not sure what is the
> issue

What is the device model you are running this on and what version of Android? And what version is running on the Xiaomi device?

(In reply to sh_zam from comment #17)
> (In reply to abhifx from comment #16)
> > (In reply to sh_zam from comment #15)
> > > I haven't had luck in reproducing this bug for the longest of times. I
> > > remember it being reported multiple times.. I wish the crash logs were more
> > > helpful, can you please do a screen capture if possible, so I can see if
> > > there is anything in the user action which causes the crash that I'm not
> > > doing.
> > 
> > Hi Shazam, This is easy to replicate on samsung device. Just create two or
> > more layers, group them and select one of the layers in group and it
> > instantly crashes. 
> > 
> > this however is not replicated in my xiaomi device. not sure what is the
> > issue
> 
> What is the device model you are running this on and what version of
> Android? And what version is running on the Xiaomi device?

Tab s7+ on android 13. apparently it is crashing on samsung Tab s8 series also and mobile too. So definitely fishy with samsung (or s pen)

Yes, could be specific to Samsung's Android 13. I can't reproduce it on my Android 10 Samsung tablet or Android 13 phone  :(

(In reply to sh_zam from comment #19)
> Yes, could be specific to Samsung's Android 13. I can't reproduce it on my
> Android 10 Samsung tablet or Android 13 phone  :(

Definitely a regression though, 5.1 series is running flawlessly. Has krita started using some obscure opengl extension which Samsungs old adreno drivers are not able to handle?

Can confirm the crashing also occurs on my Motorola Edge phone running Android 13, which has near-stock Android UI. And 5.1.5 runs perfectly on the same device, so I have doubts it's a Samsung issue.

(In reply to xeses16388 from comment #21)
> Can confirm the crashing also occurs on my Motorola Edge phone running
> Android 13, which has near-stock Android UI. And 5.1.5 runs perfectly on the
> same device, so I have doubts it's a Samsung issue.

And you're able to reproduce it the same way abhifx are?

(In reply to xeses16388 from comment #21)
> Can confirm the crashing also occurs on my Motorola Edge phone running
> Android 13, which has near-stock Android UI. And 5.1.5 runs perfectly on the
> same device, so I have doubts it's a Samsung issue.

Now that is interesting. Now i am really leaning on some opengl issue with new krita since this is occurring on Motorola also and opengl in Android is very finicky

(In reply to xeses16388 from comment #21)
> Can confirm the crashing also occurs on my Motorola Edge phone running
> Android 13, which has near-stock Android UI. And 5.1.5 runs perfectly on the
> same device, so I have doubts it's a Samsung issue.

Is this the original Motorola edge with sd chipset or latest edge 40 with dimensity chip?

Since we have troubles with reproduction of this bug and we need to get an updated device first, I shall downgrade this bug from release_blocker, because we just cannot manage to fix that in time for the release... :(

(In reply to Dmitry Kazakov from comment #25)
> Since we have troubles with reproduction of this bug and we need to get an
> updated device first, I shall downgrade this bug from release_blocker,
> because we just cannot manage to fix that in time for the release... :(

Well its a dark time for android users then. 
For sure with this bug Krita for android cannot be pushed in playstore. I will keep on testing nightly if this gets magically fixed.

Krita should definitely start considering vulkan as new backend as android drivers are tad more better with vulkan

(In reply to abhifx from comment #24)
> (In reply to xeses16388 from comment #21)
> > Can confirm the crashing also occurs on my Motorola Edge phone running
> > Android 13, which has near-stock Android UI. And 5.1.5 runs perfectly on the
> > same device, so I have doubts it's a Samsung issue.
> 
> Is this the original Motorola edge with sd chipset or latest edge 40 with
> dimensity chip?

It's a Moto Edge 30 Fusion, 12GB ram variant with snapdragon.

Okay, so I had some free time today, and went back to revisit beta 1 on my Motorola Edge 30 Fusion on Android 13. Instead of installing on my main user account, I created a second user on my phone and installed beta 1 on that account.

For some reason, I was unable to get it to crash this time. Made a bunch of strokes on different layers, transformed the layers, transformed the group folder, transformed the group folder and the layers, tried different brushes, and it still ran. Soooo...yeah, I don't know what to tell ya. I have no idea why the results were different this time.

Aaaand I switched back to my main user account, and the beta crashes resumed. This time it crashed at the welcome screen before opening anything. Yeah, I genuinely don't know what to say. These crashes are random.

(In reply to xeses16388 from comment #29)
> Aaaand I switched back to my main user account, and the beta crashes
> resumed. This time it crashed at the welcome screen before opening anything.
> Yeah, I genuinely don't know what to say. These crashes are random.

I have the same behavior on samsung tab s7+. Nice find. Still not sure what is happening.  Created a secondary user and krita was working as intended and could not crash it with my tried and tested method. So weird and it eliminates gpu driver or open GL

(In reply to xeses16388 from comment #29)
> Aaaand I switched back to my main user account, and the beta crashes
> resumed. This time it crashed at the welcome screen before opening anything.
> Yeah, I genuinely don't know what to say. These crashes are random.

Have you got krita 5.1 also installed in normal user mode? Coud it be conflicting somehow

what happens if you copy over the config directory to the other user account (maybe move it to SD card, so Android allows it)? if the second instance of Krita crashes, then we know there is something in the configs...

If you can reproduce it like this, can you please share the kritarc, or the config directory. Maybe I can reproduce it on any of my devices...

(In reply to sh_zam from comment #32)
> what happens if you copy over the config directory to the other user account
> (maybe move it to SD card, so Android allows it)? if the second instance of
> Krita crashes, then we know there is something in the configs...
> 
> If you can reproduce it like this, can you please share the kritarc, or the
> config directory. Maybe I can reproduce it on any of my devices...

The other user profile is very restrictive and I am unable to copy file

(In reply to abhifx from comment #31)
> (In reply to xeses16388 from comment #29)
> > Aaaand I switched back to my main user account, and the beta crashes
> > resumed. This time it crashed at the welcome screen before opening anything.
> > Yeah, I genuinely don't know what to say. These crashes are random.
> 
> Have you got krita 5.1 also installed in normal user mode? Coud it be
> conflicting somehow

I noticed that installing the beta on the second user account also automatically updated my stable Krita to beta on the main user, with my 5.1.5 user data intact. (I assume this is typical Android behavior that I never noticed before this.)

(In reply to abhifx from comment #33)
> (In reply to sh_zam from comment #32)
> > what happens if you copy over the config directory to the other user account
> > (maybe move it to SD card, so Android allows it)? if the second instance of
> > Krita crashes, then we know there is something in the configs...
> > 
> > If you can reproduce it like this, can you please share the kritarc, or the
> > config directory. Maybe I can reproduce it on any of my devices...
> 
> The other user profile is very restrictive and I am unable to copy file

If you're referring to accessing the Android folder in Android 13, try using a third party file manager like Solid Explorer or ZArchiver to access your Krita folder.

(In reply to xeses16388 from comment #35)
> (In reply to abhifx from comment #33)
> > (In reply to sh_zam from comment #32)
> > > what happens if you copy over the config directory to the other user account
> > > (maybe move it to SD card, so Android allows it)? if the second instance of
> > > Krita crashes, then we know there is something in the configs...
> > > 
> > > If you can reproduce it like this, can you please share the kritarc, or the
> > > config directory. Maybe I can reproduce it on any of my devices...
> > 
> > The other user profile is very restrictive and I am unable to copy file
> 
> If you're referring to accessing the Android folder in Android 13, try using
> a third party file manager like Solid Explorer or ZArchiver to access your
> Krita folder.

I did, and that still didn't work. However I tried deleting Krita 5.1 folder in Android data folder and it had no effect on crashing in regular user profile. Still no clue why its working on new user but not on existing user profile.

(In reply to abhifx from comment #36)
> (In reply to xeses16388 from comment #35)
> > (In reply to abhifx from comment #33)
> > > (In reply to sh_zam from comment #32)
> > > > what happens if you copy over the config directory to the other user account
> > > > (maybe move it to SD card, so Android allows it)? if the second instance of
> > > > Krita crashes, then we know there is something in the configs...
> > > > 
> > > > If you can reproduce it like this, can you please share the kritarc, or the
> > > > config directory. Maybe I can reproduce it on any of my devices...
> > > 
> > > The other user profile is very restrictive and I am unable to copy file
> > 
> > If you're referring to accessing the Android folder in Android 13, try using
> > a third party file manager like Solid Explorer or ZArchiver to access your
> > Krita folder.
> 
> I did, and that still didn't work. However I tried deleting Krita 5.1 folder
> in Android data folder and it had no effect on crashing in regular user
> profile. Still no clue why its working on new user but not on existing user
> profile.

Have you also tried the "Clear cache and data" it is equivalent to uninstalling and reinstalling the app? If you have not, it is fine (since you'll effectively lose the app data)

(In reply to sh_zam from comment #37)
> (In reply to abhifx from comment #36)
> > (In reply to xeses16388 from comment #35)
> > > (In reply to abhifx from comment #33)
> > > > (In reply to sh_zam from comment #32)
> > > > > what happens if you copy over the config directory to the other user account
> > > > > (maybe move it to SD card, so Android allows it)? if the second instance of
> > > > > Krita crashes, then we know there is something in the configs...
> > > > > 
> > > > > If you can reproduce it like this, can you please share the kritarc, or the
> > > > > config directory. Maybe I can reproduce it on any of my devices...
> > > > 
> > > > The other user profile is very restrictive and I am unable to copy file
> > > 
> > > If you're referring to accessing the Android folder in Android 13, try using
> > > a third party file manager like Solid Explorer or ZArchiver to access your
> > > Krita folder.
> > 
> > I did, and that still didn't work. However I tried deleting Krita 5.1 folder
> > in Android data folder and it had no effect on crashing in regular user
> > profile. Still no clue why its working on new user but not on existing user
> > profile.
> 
> Have you also tried the "Clear cache and data" it is equivalent to
> uninstalling and reinstalling the app? If you have not, it is fine (since
> you'll effectively lose the app data)

I did the reverse and installed regular krita on new user half expecting it will crash the krita nightly. But there was no effect. Both krita versions are working fine.

I have cleared data on Krita nightly on my regular user multiple times in last one year which had no effect

Signed apk of 5.2 Release Candidate has been released, if anyone wants to try that out.

(In reply to AppTest from comment #39)
> Signed apk of 5.2 Release Candidate has been released, if anyone wants to
> try that out.

I Uninstalled every krita package and installed the nightly. And it crashed. I have no clue why main user is crashing but secondary user is not

Created attachment 161759 [details]
menu corruption

Andy here. I am new to Krita. I have a Lenovo m10 pro with Android 12. 5.1.5 runs without problem.
5.2 betas and rc crash quickly at random.
I before the crash I noticed the view and image menus are corrupted. See attached

(In reply to sh_zam from comment #19)
> Yes, could be specific to Samsung's Android 13. I can't reproduce it on my
> Android 10 Samsung tablet or Android 13 phone  :(

You have an Android 13 phone? Which? Cuz I have pointed out that Android 13 Edge 30 Fusion crashes...And now we have someone indicating it crashes on Android 12 also.

To have all this information in one post, I gathered a list of devices with confirmed crashing so far:

Motorola Edge 30 Fusion, Android 13
Samsung Galaxy S23 Ultra, Android 13
Samsung Galaxy Tab S6 Lite ( https://krita-artists.org/t/i-think-i-found-a-bug-on-the-5-2-0-version-of-krita/76281 )
Samsung Galaxy Tab S7+
Samsung Galaxy Tab S8+, Android 13
Samsung Galaxy Tab S9 Ultra, Android 13 ( https://krita-artists.org/t/krita-5-2-release-candidate-is-out-please-help-us-in-another-round-of-testing/74137/110 )
Lenovo M10 Pro, Android 12

Created attachment 162485 [details]
attachment-623419-0.html

I reported the Lenovo M10 Pro, Android 12 crashes on rc2...

Since then the tablet updated to Android 13. I tried 5.2 on this when it
came out. The menu corruption, I reported, did not appear, but it seemed to
crash a lot so I went back to 5.1.

I tried 5.2 again today and it did not crash.
I will use it from now. My only issue: the touch docker has no buttons. It
is just blank white space.
Below is my system information.
/Andy
--------------------------------------------------------------
Krita

 Version: 5.2.0
 Hidpi: true

Qt

  Version (compiled): 5.15.7
  Version (loaded): 5.15.7

OS Information

  Build ABI: arm64-little_endian-lp64
  Build CPU: arm64
  CPU: arm64
  Kernel Type: linux
  Kernel Version: 4.19.157-perf+
  Pretty Productname: Android  (13.0)
  Product Type: android
  Product Version: 13.0
  Product Model: LENOVO Lenovo TB128FU

Locale

  Languages: en_GB, en_Latn_GB
  C locale: C.UTF-8
  QLocale current: en
  QLocale system: en
  QTextCodec for locale: UTF-8

OpenGL Info

  Vendor:  "Qualcomm"
  Renderer:  "Adreno (TM) 610"
  Driver version:  "OpenGL ES 3.2 V@0502.0 (GIT@5ac347592d, I5b26abddf4,
1640333948) (Date:12/24/21)"
  Shading language:  "OpenGL ES GLSL ES 3.20"
  Requested format:  QSurfaceFormat(version 3.0, options
QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize
8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8,
stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer,
swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile
QSurfaceFormat::NoProfile)
  Current format:  QSurfaceFormat(version 3.2, options
QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize
8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8,
stencilBufferSize 8, samples 0, swapBehavior
QSurfaceFormat::DefaultSwapBehavior, swapInterval 0, colorSpace
QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)
  GL version: 3.2
  Supports deprecated functions false
  Is OpenGL ES: true
  supportsBufferMapping: true
  supportsBufferInvalidation: false
  forceDisableTextureBuffers: false
  Extensions:
     GL_OES_texture_half_float
     GL_KHR_blend_equation_advanced_coherent
     GL_EXT_memory_object
     GL_OES_texture_stencil8
     GL_ARM_shader_framebuffer_fetch_depth_stencil
     GL_OES_depth24
     GL_EXT_primitive_bounding_box
     GL_EXT_debug_marker
     GL_ANDROID_extension_pack_es31a
     GL_EXT_tessellation_shader
     GL_OES_sample_variables
     GL_QCOM_alpha_test
     GL_OES_standard_derivatives
     GL_EXT_disjoint_timer_query
     GL_EXT_EGL_image_array
     GL_OES_EGL_image
     GL_OES_surfaceless_context
     GL_EXT_buffer_storage
     GL_OES_depth_texture
     GL_KHR_debug
     GL_QCOM_YUV_texture_gather
     GL_OES_EGL_image_external
     GL_EXT_blit_framebuffer_params
     GL_EXT_clip_control
     GL_EXT_sRGB_write_control
     GL_EXT_texture_cube_map_array
     GL_QCOM_shader_framebuffer_fetch_noncoherent
     GL_OES_EGL_image_external_essl3
     GL_EXT_multisampled_render_to_texture2
     GL_EXT_texture_sRGB_R8
     GL_QCOM_shader_framebuffer_fetch_rate
     GL_NV_shader_noperspective_interpolation
     GL_OES_texture_npot
     GL_EXT_read_format_bgra
     GL_OES_texture_3D
     GL_OES_rgb8_rgba8
     GL_KHR_texture_compression_astc_ldr
     GL_OES_texture_float
     GL_EXT_blend_func_extended
     GL_QCOM_tiled_rendering
     GL_EXT_memory_object_fd
     GL_EXT_geometry_shader
     GL_EXT_clip_cull_distance
     GL_AMD_compressed_ATC_texture
     GL_OES_element_index_uint
     GL_EXT_debug_label
     GL_EXT_sRGB
     GL_EXT_texture_norm16
     GL_EXT_texture_sRGB_decode
     GL_OES_texture_float_linear
     GL_EXT_copy_image
     GL_EXT_gpu_shader5
     GL_OES_vertex_half_float
     GL_OES_depth_texture_cube_map
     GL_OES_shader_multisample_interpolation
     GL_OES_get_program_binary
     GL_KHR_blend_equation_advanced
     GL_OES_packed_depth_stencil
     GL_EXT_shader_framebuffer_fetch
     GL_QCOM_texture_foveated
     GL_EXT_discard_framebuffer
     GL_EXT_EGL_image_storage
     GL_EXT_texture_format_BGRA8888
     GL_EXT_texture_format_sRGB_override
     GL_EXT_texture_filter_anisotropic
     GL_EXT_shader_io_blocks
     GL_EXT_EGL_image_external_wrap_modes
     GL_OES_vertex_array_object
     GL_OES_EGL_sync
     GL_EXT_robustness
     GL_OVR_multiview2
     GL_EXT_protected_textures
     GL_EXT_texture_border_clamp
     GL_OES_texture_half_float_linear
     GL_OES_framebuffer_object
     GL_EXT_color_buffer_float
     GL_EXT_YUV_target
     GL_OES_compressed_ETC1_RGB8_texture
     GL_EXT_external_buffer
     GL_EXT_fragment_invocation_density
     GL_EXT_multisampled_render_to_texture
     GL_QCOM_texture_foveated_subsampled_layout
     GL_EXT_texture_type_2_10_10_10_REV
     GL_OES_texture_view
     GL_EXT_color_buffer_half_float
     GL_OES_shader_image_atomic
     GL_KHR_no_error
     GL_OVR_multiview_multisampled_render_to_texture
     GL_OES_sample_shading
     GL_KHR_robust_buffer_access_behavior
     GL_OVR_multiview
     GL_EXT_texture_buffer
     GL_OES_texture_storage_multisample_2d_array
     GL_EXT_shader_non_constant_global_initializers
     GL_QCOM_validate_shader_binary
     GL_EXT_draw_buffers_indexed

QPA OpenGL Detection Info
  supportsDesktopGL: false
  supportsOpenGLES: true
  isQtPreferOpenGLES: true
  Detected renderers:
    (Supported) Adreno (TM) 610 (OpenGL ES 3.2 V@0502.0 (GIT@5ac347592d,
I5b26abddf4, 1640333948) (Date:12/24/21))

useBufferInvalidation (config option): false


Hardware Information

  GPU Acceleration: auto
  Memory: 3668 Mb
  Number of Cores: 8
  Swap Location: /data/data/org.krita/cache
  Built for: arm64+neon
  Base instruction set: arm64+neon
  Supported instruction sets: arm64+neon arm32+neon avx512bw avx512dq
avx512cd avx512f fma3+avx2 avx2 fma3+avx avx fma4 fma3+sse4.2 sse4.2 sse4.1
ssse3 sse3 sse2

Current Settings

  Current Swap Location: /data/data/org.krita/cache
  Current Swap Location writable: true
  Undo Enabled: true
  Undo Stack Limit: 200
  Use OpenGL: true
  Use OpenGL Texture Buffer: true
  Disable Vector Optimizations: false
  Disable AVX Optimizations: false
  Canvas State: OPENGL_SUCCESS
  Autosave Interval: 420
  Use Backup Files: true
  Number of Backups Kept: 1
  Backup File Suffix: ~
  Backup Location: Same Folder as the File
  Backup Location writable: false
  Resource Location:
  Use Win8 Pointer Input: false
  Use RightMiddleTabletButton Workaround: false
  Levels of Detail Enabled: false
  Use Zip64: false


Display Information
Number of screens: 1
Screen: 0
Name:
Depth: 32
Scale: 1.5
Physical DPI146.064
Logical DPI72
Physical Size: 232, 139
Position: 0, 0
Resolution in pixels: 1333x800
Manufacturer:
Model:
Refresh Rate: 60
Serial Number:


On Thu, 19 Oct 2023, 19:53 AppTest, <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=472705
>
> --- Comment #44 from AppTest <xeses16388@tastrg.com> ---
> To have all this information in one post, I gathered a list of devices with
> confirmed crashing so far:
>
> Motorola Edge 30 Fusion, Android 13
> Samsung Galaxy S23 Ultra, Android 13
> Samsung Galaxy Tab S6 Lite (
>
> https://krita-artists.org/t/i-think-i-found-a-bug-on-the-5-2-0-version-of-krita/76281
> )
> Samsung Galaxy Tab S7+
> Samsung Galaxy Tab S8+, Android 13
> Samsung Galaxy Tab S9 Ultra, Android 13 (
>
> https://krita-artists.org/t/krita-5-2-release-candidate-is-out-please-help-us-in-another-round-of-testing/74137/110
> )
> Lenovo M10 Pro, Android 12
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.

*** Bug 475665 has been marked as a duplicate of this bug. ***

*** Bug 475680 has been marked as a duplicate of this bug. ***

*** Bug 476133 has been marked as a duplicate of this bug. ***

This has to be one of the strangest bugs. Even though this is released on Play Store, we still haven't gotten a reliable trace for what could be causing this. 

The best trace we have so far is:


*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
pid: 0, tid: 5543 >>> org.krita <<<

backtrace:
  #00  pc 0x00000000003f4914  /data/app/~~s4vVKEiQg06UcFf_OnKCpg==/org.krita-mKvXqVAtIikUr2tRfRWPgA==/lib/arm64/libQt5Core_arm64-v8a.so (QCoreApplication::notifyInternal2(QObject*, QEvent*)+136) (BuildId: 2bdd3f7eab36cfc0ad5e470fffa7da3134b29a8e)
  #01  pc 0x000000000042c474  /data/app/~~s4vVKEiQg06UcFf_OnKCpg==/org.krita-mKvXqVAtIikUr2tRfRWPgA==/lib/arm64/libQt5Core_arm64-v8a.so (QTimerInfoList::activateTimers()+572) (BuildId: 2bdd3f7eab36cfc0ad5e470fffa7da3134b29a8e)
  #02  pc 0x000000000042ab44  /data/app/~~s4vVKEiQg06UcFf_OnKCpg==/org.krita-mKvXqVAtIikUr2tRfRWPgA==/lib/arm64/libQt5Core_arm64-v8a.so (QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)+424) (BuildId: 2bdd3f7eab36cfc0ad5e470fffa7da3134b29a8e)
  #03  pc 0x000000000007f804  /data/app/~~s4vVKEiQg06UcFf_OnKCpg==/org.krita-mKvXqVAtIikUr2tRfRWPgA==/lib/arm64/libplugins_platforms_qtforandroid_arm64-v8a.so (QUnixEventDispatcherQPA::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)) (BuildId: da874e365af11113bb7ac512787bbeaadd91760d)

which doesn't tell us where in Krita this is happening :(

(In reply to sh_zam from comment #49)
> This has to be one of the strangest bugs. Even though this is released on
> Play Store, we still haven't gotten a reliable trace for what could be
> causing this. 
> 
> The best trace we have so far is:
> 
> 
> *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
> pid: 0, tid: 5543 >>> org.krita <<<
> 
> backtrace:
>   #00  pc 0x00000000003f4914 
> /data/app/~~s4vVKEiQg06UcFf_OnKCpg==/org.krita-mKvXqVAtIikUr2tRfRWPgA==/lib/
> arm64/libQt5Core_arm64-v8a.so (QCoreApplication::notifyInternal2(QObject*,
> QEvent*)+136) (BuildId: 2bdd3f7eab36cfc0ad5e470fffa7da3134b29a8e)
>   #01  pc 0x000000000042c474 
> /data/app/~~s4vVKEiQg06UcFf_OnKCpg==/org.krita-mKvXqVAtIikUr2tRfRWPgA==/lib/
> arm64/libQt5Core_arm64-v8a.so (QTimerInfoList::activateTimers()+572)
> (BuildId: 2bdd3f7eab36cfc0ad5e470fffa7da3134b29a8e)
>   #02  pc 0x000000000042ab44 
> /data/app/~~s4vVKEiQg06UcFf_OnKCpg==/org.krita-mKvXqVAtIikUr2tRfRWPgA==/lib/
> arm64/libQt5Core_arm64-v8a.so
> (QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::
> ProcessEventsFlag>)+424) (BuildId: 2bdd3f7eab36cfc0ad5e470fffa7da3134b29a8e)
>   #03  pc 0x000000000007f804 
> /data/app/~~s4vVKEiQg06UcFf_OnKCpg==/org.krita-mKvXqVAtIikUr2tRfRWPgA==/lib/
> arm64/libplugins_platforms_qtforandroid_arm64-v8a.so
> (QUnixEventDispatcherQPA::processEvents(QFlags<QEventLoop::
> ProcessEventsFlag>)) (BuildId: da874e365af11113bb7ac512787bbeaadd91760d)
> 
> which doesn't tell us where in Krita this is happening :(

This is absolutely strange, although intermittently all apps in android should be sandboxed, could it be possible any other app install is causing some mayhem? maybe all people reporting bugs should list down all the apps.
I am basing this assumption based on finding that an alternative user which has minimal apps installed is running it fine. (Or android is blocking that user from accessing something)

(In reply to abhifx from comment #50)
> (In reply to sh_zam from comment #49)
> > This has to be one of the strangest bugs. Even though this is released on
> > Play Store, we still haven't gotten a reliable trace for what could be
> > causing this. 
> > 
> > The best trace we have so far is:
> > 
> > 
> > *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
> > pid: 0, tid: 5543 >>> org.krita <<<
> > 
> > backtrace:
> >   #00  pc 0x00000000003f4914 
> > /data/app/~~s4vVKEiQg06UcFf_OnKCpg==/org.krita-mKvXqVAtIikUr2tRfRWPgA==/lib/
> > arm64/libQt5Core_arm64-v8a.so (QCoreApplication::notifyInternal2(QObject*,
> > QEvent*)+136) (BuildId: 2bdd3f7eab36cfc0ad5e470fffa7da3134b29a8e)
> >   #01  pc 0x000000000042c474 
> > /data/app/~~s4vVKEiQg06UcFf_OnKCpg==/org.krita-mKvXqVAtIikUr2tRfRWPgA==/lib/
> > arm64/libQt5Core_arm64-v8a.so (QTimerInfoList::activateTimers()+572)
> > (BuildId: 2bdd3f7eab36cfc0ad5e470fffa7da3134b29a8e)
> >   #02  pc 0x000000000042ab44 
> > /data/app/~~s4vVKEiQg06UcFf_OnKCpg==/org.krita-mKvXqVAtIikUr2tRfRWPgA==/lib/
> > arm64/libQt5Core_arm64-v8a.so
> > (QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::
> > ProcessEventsFlag>)+424) (BuildId: 2bdd3f7eab36cfc0ad5e470fffa7da3134b29a8e)
> >   #03  pc 0x000000000007f804 
> > /data/app/~~s4vVKEiQg06UcFf_OnKCpg==/org.krita-mKvXqVAtIikUr2tRfRWPgA==/lib/
> > arm64/libplugins_platforms_qtforandroid_arm64-v8a.so
> > (QUnixEventDispatcherQPA::processEvents(QFlags<QEventLoop::
> > ProcessEventsFlag>)) (BuildId: da874e365af11113bb7ac512787bbeaadd91760d)
> > 
> > which doesn't tell us where in Krita this is happening :(
> 
> This is absolutely strange, although intermittently all apps in android
> should be sandboxed, could it be possible any other app install is causing
> some mayhem? maybe all people reporting bugs should list down all the apps.
> I am basing this assumption based on finding that an alternative user which
> has minimal apps installed is running it fine. (Or android is blocking that
> user from accessing something)

I did a factory reset of my device (Tab s9 Ultra) and installed only Krita. It still crashes. I removed all 3rd party bloat and it made no difference.

However, on a 2nd user profile I created on the same device just to see if it will work, somehow it doesn't crash there, it only crashes on the main profile. I've gone out of my way to try and get it to crash, installing the same apps I'd normally use, randomly clicking everything I possibly can, painting on large canvas (20000x20000), it still wont crash. 

So far, this issue is limited only to the main user profile.

(In reply to Edward Mowah from comment #51)
> (In reply to abhifx from comment #50)
> > (In reply to sh_zam from comment #49)
> > > This has to be one of the strangest bugs. Even though this is released on
> > > Play Store, we still haven't gotten a reliable trace for what could be
> > > causing this. 
> > > 
> > > The best trace we have so far is:
> > > 
> > > 
> > > *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
> > > pid: 0, tid: 5543 >>> org.krita <<<
> > > 
> > > backtrace:
> > >   #00  pc 0x00000000003f4914 
> > > /data/app/~~s4vVKEiQg06UcFf_OnKCpg==/org.krita-mKvXqVAtIikUr2tRfRWPgA==/lib/
> > > arm64/libQt5Core_arm64-v8a.so (QCoreApplication::notifyInternal2(QObject*,
> > > QEvent*)+136) (BuildId: 2bdd3f7eab36cfc0ad5e470fffa7da3134b29a8e)
> > >   #01  pc 0x000000000042c474 
> > > /data/app/~~s4vVKEiQg06UcFf_OnKCpg==/org.krita-mKvXqVAtIikUr2tRfRWPgA==/lib/
> > > arm64/libQt5Core_arm64-v8a.so (QTimerInfoList::activateTimers()+572)
> > > (BuildId: 2bdd3f7eab36cfc0ad5e470fffa7da3134b29a8e)
> > >   #02  pc 0x000000000042ab44 
> > > /data/app/~~s4vVKEiQg06UcFf_OnKCpg==/org.krita-mKvXqVAtIikUr2tRfRWPgA==/lib/
> > > arm64/libQt5Core_arm64-v8a.so
> > > (QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::
> > > ProcessEventsFlag>)+424) (BuildId: 2bdd3f7eab36cfc0ad5e470fffa7da3134b29a8e)
> > >   #03  pc 0x000000000007f804 
> > > /data/app/~~s4vVKEiQg06UcFf_OnKCpg==/org.krita-mKvXqVAtIikUr2tRfRWPgA==/lib/
> > > arm64/libplugins_platforms_qtforandroid_arm64-v8a.so
> > > (QUnixEventDispatcherQPA::processEvents(QFlags<QEventLoop::
> > > ProcessEventsFlag>)) (BuildId: da874e365af11113bb7ac512787bbeaadd91760d)
> > > 
> > > which doesn't tell us where in Krita this is happening :(
> > 
> > This is absolutely strange, although intermittently all apps in android
> > should be sandboxed, could it be possible any other app install is causing
> > some mayhem? maybe all people reporting bugs should list down all the apps.
> > I am basing this assumption based on finding that an alternative user which
> > has minimal apps installed is running it fine. (Or android is blocking that
> > user from accessing something)
> 
> I did a factory reset of my device (Tab s9 Ultra) and installed only Krita.
> It still crashes. I removed all 3rd party bloat and it made no difference.
> 
> However, on a 2nd user profile I created on the same device just to see if
> it will work, somehow it doesn't crash there, it only crashes on the main
> profile. I've gone out of my way to try and get it to crash, installing the
> same apps I'd normally use, randomly clicking everything I possibly can,
> painting on large canvas (20000x20000), it still wont crash. 
> 
> So far, this issue is limited only to the main user profile.

I was going to try this today but thanks for taking the bullet. Its clear apps are not clashing (as i thought should because of Android's nature being container based apps). 
So somehow the second user is getting some sort of restriction which is helping krita not to crash. I am completely out of clue now.

Created attachment 162738 [details]
attachment-932576-0.html

I'm not sure if it helps, but after reading this I also created a second account on a Samsung S9 tablet and installed a nightly update version (5.3). I have used it for several hours without it crashing - it appears to run without any problems at all.

Sent from Sky Yahoo Mail on Android 
 
  On Sat, 28 Oct 2023 at 12:08, bugzilla_noreply@kde.org<bugzilla_noreply@kde.org> wrote:   https://bugs.kde.org/show_bug.cgi?id=472705

--- Comment #52 from abhifx@gmail.com ---
(In reply to Edward Mowah from comment #51)
> (In reply to abhifx from comment #50)
> > (In reply to sh_zam from comment #49)
> > > This has to be one of the strangest bugs. Even though this is released on
> > > Play Store, we still haven't gotten a reliable trace for what could be
> > > causing this. 
> > > 
> > > The best trace we have so far is:
> > > 
> > > 
> > > *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
> > > pid: 0, tid: 5543 >>> org.krita <<<
> > > 
> > > backtrace:
> > >  #00  pc 0x00000000003f4914 
> > > /data/app/~~s4vVKEiQg06UcFf_OnKCpg==/org.krita-mKvXqVAtIikUr2tRfRWPgA==/lib/
> > > arm64/libQt5Core_arm64-v8a.so (QCoreApplication::notifyInternal2(QObject*,
> > > QEvent*)+136) (BuildId: 2bdd3f7eab36cfc0ad5e470fffa7da3134b29a8e)
> > >  #01  pc 0x000000000042c474 
> > > /data/app/~~s4vVKEiQg06UcFf_OnKCpg==/org.krita-mKvXqVAtIikUr2tRfRWPgA==/lib/
> > > arm64/libQt5Core_arm64-v8a.so (QTimerInfoList::activateTimers()+572)
> > > (BuildId: 2bdd3f7eab36cfc0ad5e470fffa7da3134b29a8e)
> > >  #02  pc 0x000000000042ab44 
> > > /data/app/~~s4vVKEiQg06UcFf_OnKCpg==/org.krita-mKvXqVAtIikUr2tRfRWPgA==/lib/
> > > arm64/libQt5Core_arm64-v8a.so
> > > (QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::
> > > ProcessEventsFlag>)+424) (BuildId: 2bdd3f7eab36cfc0ad5e470fffa7da3134b29a8e)
> > >  #03  pc 0x000000000007f804 
> > > /data/app/~~s4vVKEiQg06UcFf_OnKCpg==/org.krita-mKvXqVAtIikUr2tRfRWPgA==/lib/
> > > arm64/libplugins_platforms_qtforandroid_arm64-v8a.so
> > > (QUnixEventDispatcherQPA::processEvents(QFlags<QEventLoop::
> > > ProcessEventsFlag>)) (BuildId: da874e365af11113bb7ac512787bbeaadd91760d)
> > > 
> > > which doesn't tell us where in Krita this is happening :(
> > 
> > This is absolutely strange, although intermittently all apps in android
> > should be sandboxed, could it be possible any other app install is causing
> > some mayhem? maybe all people reporting bugs should list down all the apps.
> > I am basing this assumption based on finding that an alternative user which
> > has minimal apps installed is running it fine. (Or android is blocking that
> > user from accessing something)
> 
> I did a factory reset of my device (Tab s9 Ultra) and installed only Krita.
> It still crashes. I removed all 3rd party bloat and it made no difference.
> 
> However, on a 2nd user profile I created on the same device just to see if
> it will work, somehow it doesn't crash there, it only crashes on the main
> profile. I've gone out of my way to try and get it to crash, installing the
> same apps I'd normally use, randomly clicking everything I possibly can,
> painting on large canvas (20000x20000), it still wont crash. 
> 
> So far, this issue is limited only to the main user profile.

I was going to try this today but thanks for taking the bullet. Its clear apps
are not clashing (as i thought should because of Android's nature being
container based apps). 
So somehow the second user is getting some sort of restriction which is helping
krita not to crash. I am completely out of clue now.

*** Bug 475862 has been marked as a duplicate of this bug. ***

It seems like this could be happening due to something on Java side and a way to figure out might to share a logcat of app, but it requires  installing adb.  If that's not possible something like https://developer.android.com/studio/debug/bug-report might be really helpful. But due to sometimes sensitive nature of the bug-report file I’d recommend you to email it to me on: shzam [at] sdf.org

(In reply to sh_zam from comment #55)
> It seems like this could be happening due to something on Java side and a
> way to figure out might to share a logcat of app, but it requires 
> installing adb.  If that's not possible something like
> https://developer.android.com/studio/debug/bug-report might be really
> helpful. But due to sometimes sensitive nature of the bug-report file I’d
> recommend you to email it to me on: shzam [at] sdf.org

Do you have instructions on how to do the first suggestion? The adb process, for those of us with less tech knowledge.

Didn't realize the link had adb instructions. Sorry, my mistake.

ENABLING ACCESSIBILITY APPLICATIONS (SUCH AS BITWARDEN AND MICROSOFT AUTHENTICATOR) IS CAUSING KRITA TO CRASH

I backed up my device files, apps and settings and did a factory reset (Galaxy Tab S9 Ultra)
After reset, I didn't connect to any network at the beginning.
I also didn't logon to any account (Google / Samsung)
No application updates, no setting changed besides switching device to dark mode.
I uninstalled / disabled 3rd party apps / bloat like always.

Krita ran without crashing.

As soon as I restored everything from my back up including apps and device settings, krita began crashing again.

I repeated the process but this time I logged in to Google and Samsung right from the beginning after reset and even updated applications.
I uninstalled bloat like always.
But I didn't install any other application or change any settings (besides switching to dark mode)

Krita runs fine.

From here for each app installed and for each settings changed, I will opened Krita and see if it will crash.

Krita ran without crashing until I installed and set up Bitwarden on my device.

At first I thought it was just Bitwarden itself, because Krita ran fine up until I set Bitwarden up, but then Microsoft Authenticator also Caused Krita to crash.
Both apps have similar settings and one among them is enabling them in Accessibility Settings.

I found that when either app was enabled under Accessibility settings, krita crashed.
By disabling them in Accessibility settings I am able to run krita without a crash.

Can someone else who's having this issue confirm that they have any app enabled under accessibility settings? (Maybe it's not just Bitwarden and Microsoft Authenticator)

(In reply to Edward Mowah from comment #58)
> ENABLING ACCESSIBILITY APPLICATIONS (SUCH AS BITWARDEN AND MICROSOFT
> AUTHENTICATOR) IS CAUSING KRITA TO CRASH
> 
> I backed up my device files, apps and settings and did a factory reset
> (Galaxy Tab S9 Ultra)
> After reset, I didn't connect to any network at the beginning.
> I also didn't logon to any account (Google / Samsung)
> No application updates, no setting changed besides switching device to dark
> mode.
> I uninstalled / disabled 3rd party apps / bloat like always.
> 
> Krita ran without crashing.
> 
> As soon as I restored everything from my back up including apps and device
> settings, krita began crashing again.
> 
> I repeated the process but this time I logged in to Google and Samsung right
> from the beginning after reset and even updated applications.
> I uninstalled bloat like always.
> But I didn't install any other application or change any settings (besides
> switching to dark mode)
> 
> Krita runs fine.
> 
> From here for each app installed and for each settings changed, I will
> opened Krita and see if it will crash.
> 
> Krita ran without crashing until I installed and set up Bitwarden on my
> device.
> 
> At first I thought it was just Bitwarden itself, because Krita ran fine up
> until I set Bitwarden up, but then Microsoft Authenticator also Caused Krita
> to crash.
> Both apps have similar settings and one among them is enabling them in
> Accessibility Settings.
> 
> I found that when either app was enabled under Accessibility settings, krita
> crashed.
> By disabling them in Accessibility settings I am able to run krita without a
> crash.
> 
> Can someone else who's having this issue confirm that they have any app
> enabled under accessibility settings? (Maybe it's not just Bitwarden and
> Microsoft Authenticator)

Nice Find Edward, I will check the same once I reach back home and this could potentially explain why the second user is working for me as i don't have any app there with accessibility access. 
Ok while posting this I tested this on my mi11t pro which has never crashed ever, and right after giving accessibility access, right on the money krita crashed.

I can confirm that this finding is correct. Giving access to accessibility crashes Krita as per my method (add layers, group them, and select one layer)

Brawo Edward.

I will also try to take Logcat on mobile since I don't have a pc access.

This is to confirm that accessibility indeed is the root cause.

I have enabled a special bubble to control volume digitally on samsung and that was causing the crash. Tested on both nightly and 5.2.

Many thanks to @edward

@shazam, kindly look into this.

Interesting find! If this is true, it would explain why I wasn't getting crashes on the secondary user: because I went straight to installing Krita without enabling accessibility apps. I too am a user of accessibility apps daily, I got Magnification, Google Accessibility Suite, and Google Voice Access enabled. I haven't tested what turning these off does yet, but it seems the above comments are sure.

I just did some testing, and I can confirm this is an accessibility app issue. I know this because I was able to reproduce the crashing on the second user account too! Here are the steps I took to reproduce the crash:

Samsung Galaxy Tab S8 Plus
Android 13 with October 2023 security patch
Samsung One UI 5.1.1
Krita 5.2.1 arm64 apk
( https://download.kde.org/stable/krita/5.2.1/krita-arm64-v8a-5.2.1-release-signed.apk )
Accessibility app that causes crashing: Google Voice Access
( https://play.google.com/store/apps/details?id=com.google.android.apps.accessibility.voiceaccess )

1. Go to Settings -> Accessibility -> Installed Apps -> Voice Access, and turn the switch from Off to On. Be sure to setup voice access if you haven't done so (it has to download a voice file during setup), and make sure notifications for it are on. Once it's done, you'll have a notification called "Voice Access: Tap to start". Tap it, and you'll get a blue bubble with "....." on the corner to confirm it is active.

2. Do a fresh install of Krita 5.2.1, and launch it.

3. Start a new drawing with a 5000x4000 resolution. Then, on the Advanced Color Selector docker, change the brush color to anything else.

4. Krita will crash. If it doesn't, repeat step 3 until it does, without closing any open documents. (It should definitely crash after repeating step 3 two to three more times.)

5. Notice that this happens with Voice Access enabled. Now, go back to the device's setting app and turn Voice Access off (the notification should disappear).

6. This time launch Krira again, and repeat step 3 several times, without closing any open documents. You will see that it stopped crashing!

I can reproduce this on my Lenovo TB128FU. When I intially reported errors  I had the "Lenovo Pen" app enabled. I now have this off by default. This is classified as an  "accessibility app".  If I turn it on Krita will crash again.

*** Bug 476695 has been marked as a duplicate of this bug. ***

*** Bug 476695 has been marked as a duplicate of this bug. ***

Any luck with reproducing the crash with this new information, sh_zam?

*** Bug 477243 has been marked as a duplicate of this bug. ***

Git commit b8db3c10a55c98aa814fd959d119b6202380d392 by Sharaf Zaman.
Committed on 20/11/2023 at 14:41.
Pushed by szaman into branch 'master'.

Android: Fix a crash caused by QAccessibility.

There seems to be issues with QAccessibility module, where it tries to
traverse the QObject hierarchy in Android thread (when it is only
supposed to do so in Main Thread), fixing it is non-trivial and so is
testing, so we are again temporarily (until next Qt update) disabling
it :(

M  +1    -1    3rdparty/ext_qt/CMakeLists.txt

https://invent.kde.org/graphics/krita/-/commit/b8db3c10a55c98aa814fd959d119b6202380d392

Thanks a lot for the immense help! It wouldn't have been possible to fix it without it! 

I'll kick off the dependencies build, please test the nightly if possible, Halla will soon make a release with this patch :))

(In reply to sh_zam from comment #69)
> Thanks a lot for the immense help! It wouldn't have been possible to fix it
> without it! 
> 
> I'll kick off the dependencies build, please test the nightly if possible,
> Halla will soon make a release with this patch :))

Tested nightly build #1276 with the fix and it doesn't crash with accessibility apps enabled.
Thanks.

*** Bug 477549 has been marked as a duplicate of this bug. ***