Crash when painting cover images

Seb Ruiz ruiz at kde.org
Thu Jul 17 03:17:00 CEST 2008


2008/7/17 Daniel Winter <dw at danielwinter.de>:
> I added basic cover support to Nepomuk Collection and now Amarok crashes
> somewhere in Qt.
>
> Thread 1 (Thread 0xb38ff6f0 (LWP 32464)):
> #0  0xb7efc424 in __kernel_vsyscall ()
> #1  0xb7cfdacb in waitpid () from /lib/libpthread.so.0
> #2  0xb783c3a5 in Amarok::Crash::crashHandler () at /home/kde-
> devel/kdesvn/extragear/multimedia/amarok/src/CrashHandler.cpp:254
> #3  <signal handler called>
> #4  0xb4fddbb1 in QPainter::isActive () from /usr/lib/libQtGui.so.4
> #5  0xb4fe1675 in QPainter::clipPath () from /usr/lib/libQtGui.so.4
> #6  0xb5078c1f in ?? () from /usr/lib/libQtGui.so.4
> #7  0xbfa13bf8 in ?? ()
> #8  0x0a2fe830 in ?? ()
> #9  0xbfa13b90 in ?? ()
>
> I think I am missing Qt debuging symbols.
>
> The pimaps are returned that way:
>
> (in the image() function of the Albums)
>
> QPixmap img( m_imagePath );
> if ( !img.isNull() )
> {
>   return img.scaled( size, size, Qt::KeepAspectRatio,
> Qt::SmoothTransformation );
> }
>
> (yes i am doing no local caching in filesystem at the moment)
>
> Does someone know why it is crashing?
>
> Has it something to do with the Qt Pixmap cache which I am possible
> overwriting (with the image loading in the QPixmap constructor?) while the
> pixmap gets drawn?

Can you post the entire backtrace with the all thread traces?

Keep in mind that QPixmap is an on-screen representation and it is not
threadsafe, although I don't think that this is the cause for your
crash.


-- 
Seb Ruiz

http://www.sebruiz.net/


More information about the Amarok-devel mailing list