This forum has been archived. All content is frozen. Please use KDE Discuss instead.

[Bug?] Random crashes of AppImage on Xubuntu 16.04

Tags: None
(comma "," separated)
User avatar
Linus L
Registered Member
Posts
4
Karma
0
OS
Hi, I'm working with the 64-bit AppImage, downloaded from the official site. The app occasionally crashes at random. It doesn't seem tied to specific tasks or time passed.

Ran it through a terminal to see if I could catch any error messages. A see a couple of messages being spammed continuously, and the last lines before the app closed was:

Code: Select all
QAccessibleTable::child: Invalid index at:  30 0
Cannot creat accessible child interface for object:  KisUndoView(0x1679c670)  index:  30
QAccessibleTable::child: Invalid index at:  30 0
Cannot creat accessible child interface for object:  KisUndoView(0x1679c670)  index:  30
QAccessibleTable::child: Invalid index at:  30 0
Cannot creat accessible child interface for object:  KisUndoView(0x1679c670)  index:  30
QAccessibleTable::child: Invalid index at:  30 0
Cannot creat accessible child interface for object:  KisUndoView(0x1679c670)  index:  30
QAccessibleTable::child: Invalid index at:  30 0
Cannot creat accessible child interface for object:  KisUndoView(0x1679c670)  index:  30
Segmentation fault (core dumped)

System specs are as follows:
Code: Select all
Krita
  Version: 3.3.2

OS Information
  Build ABI: x86_64-little_endian-lp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: linux
  Kernel Version: 4.4.0-101-generic
  Pretty Productname: Ubuntu 16.04.3 LTS
  Product Type: ubuntu
  Product Version: 16.04

OpenGL Info
  Vendor:  NVIDIA Corporation
  Renderer:  "GeForce 6100 nForce 405/integrated/SSE2"
  Version:  "2.1.2 NVIDIA 304.135"
  Shading language:  1.20 NVIDIA via Cg compiler
  Requested format:  QSurfaceFormat(version 3.0, options QFlags(0x4), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior 2, swapInterval 0, profile  2)
  Current format:    QSurfaceFormat(version 2.1, options QFlags(0x4), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 0, stencilBufferSize 8, samples -1, swapBehavior 2, swapInterval 0, profile  0)
     Version: 2.1
     Supports deprecated functions true
     is OpenGL ES: false

I'm unsure if this is a bug with Krita in itself, or just some quirk in my current system setup.

Many thanks!
User avatar
halla
KDE Developer
Posts
5092
Karma
20
OS
That looks pretty weird. The appimage isn't built with support for accessibility, yet that's where a crash is happening, and Ubuntu 16.04 is known to have a broken Qt when it comes to accessibility... But the appimage doesn't use the system's Qt. Right now, I haven't got any idea what might be going on, but you could try to remove Qt's accessibility package from your system and see if that helps.
User avatar
Linus L
Registered Member
Posts
4
Karma
0
OS
boudewijn wrote:That looks pretty weird. The appimage isn't built with support for accessibility, yet that's where a crash is happening, and Ubuntu 16.04 is known to have a broken Qt when it comes to accessibility... But the appimage doesn't use the system's Qt. Right now, I haven't got any idea what might be going on, but you could try to remove Qt's accessibility package from your system and see if that helps.

Thanks, I'll try to purge it. It might be a red herring, though, I got another crash without the preceding calls to QAccessibleTable:

Code: Select all
...
QIODevice::write (QFile, "log/Ink_tilt_20.stroke.rdata"): device not open
QIODevice::write (QFile, "log/Ink_tilt_20.stroke.rdata"): device not open
QIODevice::write (QFile, "log/Ink_tilt_20.stroke.rdata"): device not open
Segmentation fault (core dumped)

The QIODevice is one of those messages that get spammed to the console continuously, so I doubt it contributes to the crashes, though I guess it support the theory that the AppImage tries to use older Qt packages lingering on the system.
User avatar
halla
KDE Developer
Posts
5092
Karma
20
OS
Um... You probably should disable performance logging.
User avatar
Linus L
Registered Member
Posts
4
Karma
0
OS
boudewijn wrote:Um... You probably should disable performance logging.


Aha, that's what that is, thanks!

Ok, I've been running Krita a couple of times now (for multiple hours) after purging any lingering Qt-package I could find on my system, and I've thus far not encountered any segmentation faults (or other sudden app crashes).

If you're interested in gathering info on AppImages conflicting with system Qt-packages, I'm happy to help out. If not, I've marked this thread as solved. Thank you very much for your feedback! :)
User avatar
halla
KDE Developer
Posts
5092
Karma
20
OS
Yes, we really should have a bug for this on bugs.kde.org with as exact a list as possible of what Qt packages you had got installed.
User avatar
Linus L
Registered Member
Posts
4
Karma
0
OS
Editing this post since my latest crash introduced a call to QAccessibleTable again.

Code: Select all
...
QAccessibleTable::child: Invalid index at:  31 0
Cannot creat accessible child interface for object:  KisUndoView(0x15bb7f90)  index:  31
QAccessibleTable::child: Invalid index at:  31 0
Cannot creat accessible child interface for object:  KisUndoView(0x15bb7f90)  index:  31
QAccessibleTable::child: Invalid index at:  31 0
Cannot creat accessible child interface for object:  KisUndoView(0x15bb7f90)  index:  31
Segmentation fault (core dumped)


I have not reinstalled the Qt-packages. I'm closing this thread in favour of the bug report at https://bugs.kde.org/show_bug.cgi?id=388495.


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], Sogou [Bot]