100% CPU while searching in collection browser

Fri Feb 22 00:10:38 UTC 2008

Any suggestions?  Anyone else think it is weird that "marshall" crashes Amarok?

This happens on 3 separate machines, all Fedora 8.  I've done a
complete rebuild of the collection DB, didn't help.

I'd also love to figure out why I get no debug info even when
compiling with --enable-debug=full

Thanks
Andy

On Sun, Feb 10, 2008 at 6:31 PM, Dr. Diesel <dr.diesel at gmail.com> wrote:
> A bit more information, whenever I type "marshall" into the collection
>  browser search, I get the 100% cpu problem every time?
>
>  If I type "the marshall" it does not happen.
>
>  Any way to track this further?
>
>  Thanks
>  Andy
>
>
>
>  On Jan 26, 2008 10:00 PM, Dr. Diesel <dr.diesel at gmail.com> wrote:
>  > And again, 10% CPU but responsive.
>  >
>  > [garage at localhost ~]$ amarokapp
>  > DCOPClient::attachInternal. Attach failed Could not open network socket
>  > kbuildsycoca running...
>  > QLayout "unnamed" added to QVBox "unnamed", which already has a layout
>  > QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to
>  > layout for PlaylistWindow/PlaylistWindow
>  > QObject::connect: Incompatible sender/receiver arguments
>  >         StarManager::ratingsColorsChanged() -->
>  > ContextBrowser::ratingOrScoreOrLabelsChanged(const QString&)
>  > STARTUP
>  > QImage::smoothScale: Image is a null image
>  > QImage::smoothScale: Image is a null image
>  > QImage::smoothScale: Image is a null image
>  > QImage::smoothScale: Image is a null image
>  > QImage::smoothScale: Image is a null image
>  > QImage::smoothScale: Image is a null image
>  > QImage::smoothScale: Image is a null image
>  > QImage::smoothScale: Image is a null image
>  > QImage::smoothScale: Image is a null image
>  > QImage::smoothScale: Image is a null image
>  > QImage::smoothScale: Image is a null image
>  > QImage::smoothScale: Image is a null image
>  > kbuildsycoca running...
>  > Reusing existing ksycoca
>  > DCOP Cleaning up dead connections.
>  > QImage::smoothScale: Image is a null image
>  > QImage::smoothScale: Image is a null image
>  > QImage::smoothScale: Image is a null image
>  > QImage::smoothScale: Image is a null image
>  > kbuildsycoca running...
>  > Reusing existing ksycoca
>  > DCOP Cleaning up dead connections.
>  > kbuildsycoca running...
>  > Reusing existing ksycoca
>  > DCOP Cleaning up dead connections.
>  > kbuildsycoca running...
>  > Reusing existing ksycoca
>  > DCOP Cleaning up dead connections.
>  > kbuildsycoca running...
>  > Reusing existing ksycoca
>  > kbuildsycoca running...
>  > Reusing existing ksycoca
>  > kbuildsycoca running...
>  > Reusing existing ksycoca
>  > kbuildsycoca running...
>  > Reusing existing ksycoca
>  > kbuildsycoca running...
>  > Reusing existing ksycoca
>  > DCOP Cleaning up dead connections.
>  > kbuildsycoca running...
>  > Reusing existing ksycoca
>  > kbuildsycoca running...
>  > Reusing existing ksycoca
>  > kbuildsycoca running...
>  > Reusing existing ksycoca
>  > DCOP Cleaning up dead connections.
>  > kbuildsycoca running...
>  >
>  >
>  >
>  > On Jan 26, 2008 10:38 AM, Dr. Diesel <dr.diesel at gmail.com> wrote:
>  > > Sorry, forgot the previous message!!
>  > >
>  > > Mark's suggestion at the bottom.
>  > >
>  > >
>  > > On Jan 26, 2008 10:25 AM, Dr. Diesel <dr.diesel at gmail.com> wrote:
>  > > > This doesn't look too helpful, but here it is.  In this situation the
>  > > > CPU was hung at 100% but Amarok would still respond normally.  At
>  > > > least appeard to.  The 100% Amarok Hang hasn't occurred lately.
>  > > >
>  > > > I'll keep trying!
>  > > >
>  > > > [garage at localhost ~]$ amarokapp
>  > > > kbuildsycoca running...
>  > > > DCOP Cleaning up dead connections.
>  > > > QLayout "unnamed" added to QVBox "unnamed", which already has a layout
>  > > > QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to
>  > > > layout for PlaylistWindow/PlaylistWindow
>  > > > QObject::connect: Incompatible sender/receiver arguments
>  > > >         StarManager::ratingsColorsChanged() -->
>  > > > ContextBrowser::ratingOrScoreOrLabelsChanged(const QString&)
>  > > > STARTUP
>  > > > QImage::smoothScale: Image is a null image
>  > > > QImage::smoothScale: Image is a null image
>  > > > QColor::setRgb: RGB parameter(s) out of range
>  > > > QColor::setRgb: RGB parameter(s) out of range
>  > > > QColor::setRgb: RGB parameter(s) out of range
>  > > > QColor::setRgb: RGB parameter(s) out of range
>  > > > QImage::smoothScale: Image is a null image
>  > > > QImage::smoothScale: Image is a null image
>  > > > QImage::smoothScale: Image is a null image
>  > > > QImage::smoothScale: Image is a null image
>  > > > QImage::smoothScale: Image is a null image
>  > > > QImage::smoothScale: Image is a null image
>  > > > QImage::smoothScale: Image is a null image
>  > > > QImage::smoothScale: Image is a null image
>  > > > QImage::smoothScale: Image is a null image
>  > > > QImage::smoothScale: Image is a null image
>  > > > QImage::smoothScale: Image is a null image
>  > > > QImage::smoothScale: Image is a null image
>  > > > QImage::smoothScale: Image is a null image
>  > > > QImage::smoothScale: Image is a null image
>  > > > Terminated
>  > > > [garage at localhost ~]$ X Error: BadWindow (invalid Window parameter) 3
>  > > >   Major opcode:  7
>  > > >   Minor opcode:  0
>  > > >   Resource id:  0x3600052
>  > > > process 24308: arguments to dbus_message_new_method_call() were
>  > > > incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file
>  > > > dbus-message.c line 1074.
>  > > > This is normally a bug in some application using the D-Bus library.
>  > > >   D-Bus not built with -rdynamic so unable to print a backtrace
>  > > > Last DCOP call before KDED crash was from application 'DCOPServer'
>  > > > to object 'kded', function 'quit()'.
>  > > > KCrash: Application 'kded' crashing...
>  > > > Warning: connect() failed: : No such file or directory
>  > > > KCrash cannot reach kdeinit, launching directly.
>  > > > kbuildsycoca running...
>  > > > DCOP Cleaning up dead connections.
>  > > > [garage at localhost ~]$
>  > > >
>  > > >
>  > > On 1/13/08, Dr. Diesel <dr.diesel at gmail.com> wrote:
>  > > > Any help suggestions etc, this is driving me nuts!!!
>  > > >
>  > > > Anyway to determine which thread/procedure/function is looped when
>  > > > this happens?  Surly there is more information I can provide!!
>  > > >
>  > > > On Dec 6, 2007 5:32 PM, Dr. Diesel <dr.diesel at gmail.com> wrote:
>  > > > > This happens about every 10-15 searches.  100% CPU for about 3-5
>  > > > > minutes from amarokapp, then all back to normal?
>  > > > >
>  > > > > Running today's SVN, but this has happened for possible the last 30 days.
>  > > > >
>  > > > > Running Fedora 8, mysql with 150K files.  Normally each search is
>  > > > > about 2-5 seconds.
>  > >
>  > > Hi Andy, try to rebuild Amarok with --enable-debug=full, and then
>  > > start amarokapp from the shell. You will notice a great amount of
>  > > debug information printed to the terminal, including timing
>  > > information.
>  > >
>  > > When the problems occurs again, see if you can find anything
>  > > interesting in the debug info, or paste it here for us to analyze.
>  > >
>  > > --
>  > > Mark
>  > >
>  >
>  >
>  >
>  >
>  > --
>  > projecthuh.com
>  > All of my bits are free, are yours?  Fedoraproject.org
>  >
>
>
>
>  --
>  projecthuh.com
>  All of my bits are free, are yours?  Fedoraproject.org
>

-- 
projecthuh.com
All of my bits are free, are yours? Fedoraproject.org