| Summary: | Krita crash on save | ||
|---|---|---|---|
| Product: | [Applications] krita | Reporter: | connorpickett |
| Component: | General | Assignee: | Krita Bugs <krita-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | amy, halla, marcus, shzam |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 5.0.6 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
connorpickett
2022-05-27 17:47:59 UTC
*** This bug has been marked as a duplicate of bug 453884 *** > Saving a new file causes Krita to crash every time. Others have suggested rolling back kxmlgui but I do not have that package installed.
hmm weird, can you share the `/proc/<krita's-pid>/maps` file?
Created attachment 149732 [details]
New crash information added by DrKonqi
krita (5.0.5) using Qt 5.15.4
Using the save dialogue - such as from the "Save As..." or "Export..." menu options - produces the crash.
When opening an existing file and using the "Save" menu option, no crash happens.
Seems to be confirmed in the backtrace in the `KisPreviewFileDialog` destructor.
-- Backtrace (Reduced):
#4 0x00007f4fcf30ec47 in std::__atomic_base<int>::load (__m=std::memory_order_relaxed, this=0x2ffffffff) at /usr/include/c++/9/bits/atomic_base.h:413
#5 QAtomicOps<int>::loadRelaxed<int> (_q_value=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic_cxx11.h:239
#6 QBasicAtomicInteger<int>::loadRelaxed (this=0x2ffffffff) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:107
[...]
#8 QList<QAction*>::~QList (this=0x55849ceed240, __in_chrg=<optimized out>) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:873
#9 0x00007f4fcf39878c in KToolBar::Private::~Private (this=0x55849ceed190, __in_chrg=<optimized out>) at ./libs/widgetutils/xmlgui/ktoolbar.cpp:83
Ah, looks like it's solved in the duplicated ticket. Sorry for the noise. I made a 5.0.8 for linux distributions to avoid this issue. |