https://bugs.kde.org/show_bug.cgi?id=443347
Tiar changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=443347
--- Comment #7 from David REVOY ---
Hi Dmitry, yes same feeling. My intuition would be to invite you close it for
now.
I haven't saw this bug again since creation of bug ticket start october and I
spent hundred hours in Krita Plus.
We can still
https://bugs.kde.org/show_bug.cgi?id=443347
--- Comment #6 from Dmitry Kazakov ---
Hi, David!
I'm tempted to declare this crash as a duplicate of this bug 444516. Given that
the backtrace shows some kind of memory corruption, it might be very related...
If you don't have this crash again, say,
https://bugs.kde.org/show_bug.cgi?id=443347
--- Comment #5 from Dmitry Kazakov ---
Hi, David!
Yes, this huge log is an expected behavior from ASAN, which can be disabled by
exporting an environment variable before running Krita:
```
export ASAN_OPTIONS=detect_leaks=0
```
Basically, ASAN tries
https://bugs.kde.org/show_bug.cgi?id=443347
--- Comment #4 from David REVOY ---
Created attachment 143649
--> https://bugs.kde.org/attachment.cgi?id=143649=edit
ASAN SUMMARY: AddressSanitizer: 88456835 byte(s) leaked in 23362 allocation(s).
Hey @dmitryk,
I tried to test and reproduce the
https://bugs.kde.org/show_bug.cgi?id=443347
--- Comment #3 from Dmitry Kazakov ---
I cannot reproduce this crash even with ASAN :(
And the backtrace looks extremely weird
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443347
Dmitry Kazakov changed:
What|Removed |Added
Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com
CC|
https://bugs.kde.org/show_bug.cgi?id=443347
Tiar changed:
What|Removed |Added
CC||tamtamy.tym...@gmail.com
Keywords|
https://bugs.kde.org/show_bug.cgi?id=443347
til.schmit...@gmx.de changed:
What|Removed |Added
CC||til.schmit...@gmx.de
--- Comment #1 from
