| Summary: | Random crash when I close krita after saving a file | ||
|---|---|---|---|
| Product: | [Applications] krita | Reporter: | Odysseas <xb_creations> |
| Component: | General | Assignee: | Krita Bugs <krita-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | halla, ochoa.juancarlos, sven.langkamp, xb_creations |
| Priority: | NOR | ||
| Version: | 2.8 Pre-Alpha | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | http://commits.kde.org/calligra/0080fc15a49a683b348c4dd80dce045a49b810cf | Version Fixed In: | |
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
Odysseas
2013-07-22 21:33:15 UTC
Created attachment 81326 [details]
New crash information added by DrKonqi
krita (2.8 Pre-Alpha) on KDE Platform 4.10.5 using Qt 4.8.4
- What I was doing when the application crashed:
Saved psd file. Unusual behavior I noticed was that the fav palette did not function- both in full screen and normal screen mode.
- Custom settings of the application:
opengl active
-- Backtrace (Reduced):
#6 0x00007f6793909037 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#7 0x00007f679390c698 in __GI_abort () at abort.c:90
[...]
#11 0x00007f6794cbbb06 in qt_assert (assertion=assertion@entry=0x7f6777d22a36 "_ref == 0", file=file@entry=0x7f6777d229e8 "/build/buildd/krita-testing-2+git20130719+r74129-41/krita/image/kis_shared.cc", line=line@entry=54) at global/qglobal.cpp:2021
#12 0x00007f6777c6daf0 in KisShared::~KisShared (this=0x62e5f60, __in_chrg=<optimized out>) at /build/buildd/krita-testing-2+git20130719+r74129-41/krita/image/kis_shared.cc:54
#13 0x00007f676fe20958 in KisBrush::~KisBrush (this=0x62e5f50, __in_chrg=<optimized out>) at /build/buildd/krita-testing-2+git20130719+r74129-41/krita/plugins/paintops/libbrush/kis_brush.cpp:158
Is the crash reproducible? Hi Odysseas, Can you try to update your build and reproduce? Created attachment 82835 [details]
New crash information added by DrKonqi
krita (2.8 Pre-Alpha) on KDE Platform 4.10.5 using Qt 4.8.4
- What I was doing when the application crashed: Closing Krita, every single time for the last week or so this has happened.
-- Backtrace (Reduced):
#10 0x00007f34d8c255a0 in KisShared::~KisShared (this=0x331aae90, __in_chrg=<optimized out>) at /build/buildd/krita-testing-2+git20130918+r74434-40/krita/image/kis_shared.cc:54
#11 0x00007f34d0d3a5c8 in KisBrush::~KisBrush (this=0x331aae80, __in_chrg=<optimized out>) at /build/buildd/krita-testing-2+git20130918+r74434-40/krita/plugins/paintops/libbrush/kis_brush.cpp:158
#12 0x00007f34d0d468f9 in KisGbrBrush::~KisGbrBrush (this=0x331aae80, __in_chrg=<optimized out>) at /build/buildd/krita-testing-2+git20130918+r74434-40/krita/plugins/paintops/libbrush/kis_gbr_brush.cpp:152
#13 0x00007f34d0d405be in qDeleteAll<QList<KisBrush*>::const_iterator> (end=..., begin=...) at /usr/include/qt4/QtCore/qalgorithms.h:322
#14 qDeleteAll<QList<KisBrush*> > (c=...) at /usr/include/qt4/QtCore/qalgorithms.h:330
*** Bug 326067 has been marked as a duplicate of this bug. *** Hi Odysseas, Do you have any custom brushes installed? .gbr files specifically? Git commit 0080fc15a49a683b348c4dd80dce045a49b810cf by Boudewijn Rempt. Committed on 30/10/2013 at 15:08. Pushed by rempt into branch 'master'. Do not delete shared pointer-based resources Related: bug 326067 M +0 -7 krita/plugins/paintops/libbrush/kis_brush_server.cpp M +60 -51 libs/widgets/KoResourceServer.h http://commits.kde.org/calligra/0080fc15a49a683b348c4dd80dce045a49b810cf Greetings Boudewijn, I am really sorry for my long absence! I now have some time to go on with Krita. So, after the new update I didn't have any crashes or corrupted files. Especially after the recent update from kubuntu 13.04 to 13.10, Krita seems to be more stable than the OS!(if something like this is possible) So now I mainly deal with plasma desktop crashing, software not working anymore properly, and a quite slower system....but Krita is running like a champion! (so far) (In reply to comment #2) > Is the crash reproducible? Not anymore! In the older built I sometimes was able to reproduce it by working on large files and opengl on. Thanks for confirming! Created attachment 83259 [details]
New crash information added by DrKonqi
krita (2.8 Pre-Alpha) on KDE Platform 4.11.2 using Qt 4.8.4
- What I was doing when the application crashed:
Krita was idle for several minutes with a file open, I pressed the 'x' button to close and asked me if I wanted to save the file.
I saved, pressed the 'x' button again and then came the crash report.
- Custom settings of the application:
Custom brushes including captured brushes (*.gbr)
-- Backtrace (Reduced):
#6 0x00007f31874a6f77 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#7 0x00007f31874aa5e8 in __GI_abort () at abort.c:90
[...]
#11 0x00007f318885f4c6 in qt_assert (assertion=assertion@entry=0x7f316ba14fb6 "_ref == 0", file=file@entry=0x7f316ba14f68 "/build/buildd/krita-testing-2+git20130808+r74237-41/krita/image/kis_shared.cc", line=line@entry=54) at global/qglobal.cpp:2021
#12 0x00007f316b9607f0 in KisShared::~KisShared (this=0x4f1fc40, __in_chrg=<optimized out>) at /build/buildd/krita-testing-2+git20130808+r74237-41/krita/image/kis_shared.cc:54
#13 0x00007f3163b4a708 in KisBrush::~KisBrush (this=0x4f1fc30, __in_chrg=<optimized out>) at /build/buildd/krita-testing-2+git20130808+r74237-41/krita/plugins/paintops/libbrush/kis_brush.cpp:158
:( I spoke too soon! This crash happened some hours later with an average-sized file of 4000x 4000 px and 3-4 layers. Luckily the file was saved normally and was not corrupted like the previous times. With which version of Krita was that? And do you have a new backtrace for me? (In reply to comment #13) > With which version of Krita was that? And do you have a new backtrace for me? Hi Boudewijn, The Krita version and crash information is in the comment 11 Can I provide you with something else? Ah, I was wondering whether you've got a new version installed. I did fix some possible issues there yesterday. |