| Summary: | Krita Crashes every 3 to 5 minutes (auto-save IS off) | ||
|---|---|---|---|
| Product: | [Applications] krita | Reporter: | Smittie <bugs.kde> |
| Component: | General | Assignee: | Krita Bugs <krita-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | halla, mpredosin |
| Priority: | NOR | ||
| Version: | 2.6.3 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
|
Description
Smittie
2013-05-21 13:56:20 UTC
This looks suspicious: #6 QHash<int, QVariant>::findNode (this=this@entry=0x20, ahp=ahp@entry=0x0, akey=<optimized out>) at /usr/include/qt4/QtCore/qhash.h:884 #7 0x00007f7dac724821 in contains (this=0x20, akey=<optimized out>) at /usr/include/qt4/QtCore/qhash.h:874 #8 KoResourceManager::setResource (this=0x20, key=key@entry=6002, value=...) at /build/buildd/calligra-2.6.3/libs/flake/KoResourceManager_p.cpp:32 #9 0x00007f7dac7254f4 in KoCanvasResourceManager::setResource (this=0x220a780, key=key@entry=6002, value=...) at /build/buildd/calligra-2.6.3/libs/flake/KoCanvasResourceManager.cpp:55 Where an object has address 0x20 -- but what can cause that? This is the first time I see this backtrace or hear of this problem on Ubuntu... there must be something strange with the setup... The setup is a System76 Ratel with an i7 cpu, 8 gigs of RAM. Kubuntu was installed using a 13.04 LiveUSB. Thunderbird mail app is the only non KDE software that has been added. If there is anything strange about the setup, it got there through KDE. Nothing has been altered from the default software install save to add users through the normal admin interface. If there are specific questions about the setup, please comment them here. I am happy to provide any additional details that will help resolve the issue. It's fairly common to see addresses that don't correlate to physical memory when the compiler has optimized and in-lined the code. Thread 1 (Thread 0x7f7db135c7c0 (LWP 14292)): [KCrash Handler] #6 QHash<int, QVariant>::findNode (this=this@entry=0x20, ahp=ahp@entry=0x0, akey=<optimized out>) at /usr/include/qt4/QtCore/qhash.h:884 #7 0x00007f7dac724821 in contains (this=0x20, akey=<optimized out>) at /usr/include/qt4/QtCore/qhash.h:874 #8 KoResourceManager::setResource (this=0x20, key=key@entry=6002, value=...) at /build/buildd/calligra-2.6.3/libs/flake/KoResourceManager_p.cpp:32 #9 0x00007f7dac7254f4 in KoCanvasResourceManager::setResource (this=0x220a780, key=key@entry=6002, value=...) at /build/buildd/calligra-2.6.3/libs/flake/KoCanvasResourceManager.cpp:55 In this case, it appears that the KoResourceManager::setResource in frame 8 has been in-lined. Try disabling optimizations, re-running the scenario and see if you get the same problem. I believe that the most concise scenario is attempting to edit an existing image file that is located in a directory in another user's home directory. The image file has permissions that allow all users to read the file, group and owner to read/write the file. I'm trying to setup a way to reproduce, but haven't managed yet,sorry. I also saw you pass by on irc in my backlog, but I was asleep :-(. This issue is pretty constant on my system. I go through the bug reporting process everytime but it is a duplicate to either this bug or another one (I didn't write down the number) that already has 20 dups. I'm inclined to think that this is probably also a dup to that one common issue. hm, and if it's a duplicate to another bug, does the backtrace contain something related to autosave? Could you try to disable autosave in the settings and see what happens? I will turn off autosave in Krita this evening (I'm Pacific Daylight Time). I will update this bug by end of week. Ok. thanks for helping to investigate (I'm in CEST, btw) A possible point of distinction. I do not see this problem on my system at work where I upgrade from Kubuntu 12.10 to Kubuntu 13.04. The system at home was a clean install from a Kubuntu 13.04 LiveUSB. Turned off auto-save. Crash still occurs. I suspect that this is either a dup of or related to bug #310310. This issue does not appear to reproduce on Kubuntu 12.10, KDE 4.9.5, Krita 2.5.3. Hi... Would it be possible for you to test with Krita Lime? http://dimula73.blogspot.nl/2013/05/krita-lime-ppa-always-fresh-versions.html -- I have a potential fix in that version. . At this time I do not have a system that I can do this on. I've taken everything back to 12.10 which is a lot more stable. I will try to figure something out. I got Kubuntu 13.04 installed on a separate hard drive, connected to the computer via USB. I got Krita Lime installed. Over a one hour period we did not see the system crash that we filed the bug on. We did see a system freeze which ultimately resulted in a 'terminate' message.
Results of 'krita -v':
Compiled for arch: ::Vc::AVXImpl
Features supported:
"SSE2" --- yes
"SSE3" --- yes
"SSSE3" --- yes
"SSE4.1" --- yes
"SSE4.2" --- yes
"SSE4a" --- no
"AVX " --- yes
Qt: 4.8.4
KDE Development Platform: 4.10.3
Krita: 2.8 Pre-Alpha
Console output when Krita is run from the console. This instantiation did NOT result in a freeze:
null@kubuntu13:~/Documents$ krita
Compiled for arch: ::Vc::AVXImpl
Features supported:
"SSE2" --- yes
"SSE3" --- yes
"SSSE3" --- yes
"SSE4.1" --- yes
"SSE4.2" --- yes
"SSE4a" --- no
"AVX " --- yes
QCoreApplication::postEvent: Unexpected null receiver
QCoreApplication::postEvent: Unexpected null receiver
krita(4247)/krita (core): Missing name attribute for tag "date"
krita(4247)/krita (core): Schema already exist uri: "http://ns.adobe.com/xap/1.0/rights/"
krita(4247)/krita (core): Schema already exist uri: "http://ns.adobe.com/exif/1.0/"
krita(4247)/krita (core): Missing name attribute for tag "date"
krita(4247)/krita (core): Schema already exist uri: "http://ns.adobe.com/xap/1.0/"
krita(4247)/krita (core): Schema already exist uri: "http://www.calligra.org/krita/xmp/MakerNote/1.0/"
krita(4247)/krita (core): Schema already exist uri: "http://ns.adobe.com/xap/1.0/mm/"
krita(4247)/krita (core): Schema already exist uri: "http://purl.org/dc/elements/1.1/"
krita(4247)/krita (core): Schema already exist uri: "http://ns.adobe.com/tiff/1.0/"
krita(4247)/krita (core): Schema already exist uri: "http://krita.org/exrchannels/1.0/"
X Error: BadAtom (invalid Atom parameter) 5
Major opcode: 20 (X_GetProperty)
Resource id: 0x0
X Error: BadAtom (invalid Atom parameter) 5
Major opcode: 20 (X_GetProperty)
Resource id: 0x0
WARNING (KoResourceItemChooser::updatePreview): the resource "2B pencil Grain 2 b" has created a non-rgb32 image thumbnail. It may not work properly.
WARNING (KoResourceItemChooser::updatePreview): the resource "2B pencil Grain 2 b" has created a non-rgb32 image thumbnail. It may not work properly.
connect failed: No such file or directory
krita(4247)/kdeui (kdelibs): No such XML file "/home/machiko/.kde/share/apps/"
QPixmap::scaled: Pixmap is a null pixmap
QGridLayout: Multi-cell fromRow greater than toRow
QCoreApplication::postEvent: Unexpected null receiver
QCoreApplication::postEvent: Unexpected null receiver
Given that we originally could not run Krita for more than 3 to 5 minutes without a crash, I am inclined to think the issue we were seeing is fixed. We did see other problems that have made us decide to continue using 12.10 and related versions for the time being.
Thanks for testing! |