Bug 731213

Description of problem:
Amarok is killed by signal 11 if I'm listening to a song and search my collection for something that's not there; either a typo such as "Lynr" instead of "Lynyrd" or searching for an album I don't have on my hdd at the moment.

Version-Release number of selected component (if applicable):
2.4.1-1.fc14.i686

How reproducible:

It does not seem to reproduce if I type gibberish into the search collection pane, like "ASdasasfd".  

It happens regardless of what file format I'm playing/searching for.

It doesn't always happen on the first search.  Sometimes it won't crash until I've purposely searched for a non-existent item a few times.  There doesn't seem to be a constant number of times that it always happens, but it's always happened in less than six searches.

It doesn't seem to happen if you type the incorrect search term too quick.  For instance, if I type "Lyn" I see "Stephen Lynch" "Lynyrd Skynyrd" and some tracks featuring David Lynch.  If I add an r so the search string is "Lynr" all of the results are eliminated and Amarok crashes.

Does not reproduce if you only have one album by the artist you are searching for.

This only reproduces when Amarok is playing a song while you search.

Steps to Reproduce:
1. Open Amarok
2. Start playing a music file (has happened with both ogg and mp3).
3. Start searching for an artist with many albums in your collection, or many artists with a similar name.
4. Type a letter or character that will eliminate all results.
  
Actual results:
Amarok would show no results, and possibly mock my spelling.

Expected results:
Amarok crashes.

Additional info:
Attached is the backtrace from gdb.  I'd be more than happy to include any needed info, files.  I'd also be willing to test any patches/suggestions or anything else I can do to assist with this.  Thanks.
-Chris