abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 33461 bytes
cmdline: wireshark
comment: I noticed when running top that kryptd was using about 43% of CPU at time of crash (since I have 2 cpus this probably means it was using almost all of one core I think).  I have never seen it as high as that before - when transferring large files between disks before about 15% very roughly is the highest I remember ever seeing it.  Don't know if this is significant or not.
component: wireshark
Attached file: coredump, 1211326464 bytes
crash_function: packet_list_compare_records
executable: /usr/sbin/wireshark
kernel: 2.6.35.11-83.fc14.x86_64
package: wireshark-gnome-1.4.3-1.fc14
rating: 4
reason: Process /usr/sbin/wireshark was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1299552018
uid: 500

How to reproduce
-----
1.  Take a (large? ~ 800MB) capture on a machine using luks encryption for the whole filesystem (except /boot of course), filter it to show only a small (94?) number of packets
2.  Click on the column to sort it (by MAC address?)
3.  Press stop because it is taking too long (i didn't expect it to sort all packets including those not displayed)
4.  Change to another workspace to run top command