wireshark: wireshark crashes clicking "OK" in the "Open File" dialog, and when captures receive lots of packets

[smith.kennedy macosforge@…]

When I run Wireshark, and I try to open an existing capture file, wireshark crashes when I click on the "OK" button in the Open dialog. This is written out to the shell where I started it:

smitty@Smittys-MacBook-Pro ~$ sudo wireshark The program 'wireshark' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'.

(Details: serial 12975 error_code 8 request_code 152 minor_code 4) (Note to programmers: normally, X errors are reported asynchronously;

that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)

Unfortunately, trying to run it in gdb didn't seem to help me figure out the underlying cause. I don't know how to look up X Window System error codes. I also remember it crashing when I would be doing a capture

Interestingly, if I run wireshark like this:

$ sudo wireshark -r mySampleFile

it opens up the file just fine. So the problem is likely in something outside wireshark (dependent library).

Similarly, if I run wireshark and start a capture, it will capture packets just fine. But when the number of captured packets is longer than what can be presented in the window, and would force the user to use the scrollbar to see the bottom, it crashes. I can make it crash earlier by making the window smaller (quiet network at home allows me to recognize this). The dumps to my terminal window when it does that seems to vary:

smitty@Smittys-MacBook-Pro ~$ sudo wireshark Password: The program 'wireshark' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'.

(Details: serial 23365 error_code 8 request_code 152 minor_code 4) (Note to programmers: normally, X errors are reported asynchronously;

that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)

smitty@Smittys-MacBook-Pro ~$ sudo wireshark The program 'wireshark' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'.

(Details: serial 33554 error_code 8 request_code 152 minor_code 4) (Note to programmers: normally, X errors are reported asynchronously;

that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)

smitty@Smittys-MacBook-Pro ~$ sudo wireshark The program 'wireshark' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'.

(Details: serial 27658 error_code 8 request_code 152 minor_code 4) (Note to programmers: normally, X errors are reported asynchronously;

that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)

smitty@Smittys-MacBook-Pro ~$ sudo wireshark Password: The program 'wireshark' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'.

(Details: serial 22309 error_code 8 request_code 152 minor_code 4) (Note to programmers: normally, X errors are reported asynchronously;

that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)

smitty@Smittys-MacBook-Pro ~$

[smith.kennedy macosforge@…]

Apple System Profiler profile