https://bugs.kde.org/show_bug.cgi?id=472705

--- Comment #51 from Edward Mowah <edwardmo...@gmail.com> ---
(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.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to