Description of problem: I saved a pretty small capture (with compress enabled) and then Wireshark just crashed. It did save the capture and WS can open it fine. Version-Release number of selected component: wireshark-gnome-1.8.3-4.fc18 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: wireshark crash_function: strlen kernel: 3.6.7-5.fc18.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #0 strlen at ../sysdeps/x86_64/multiarch/strlen-sse4.S:31 : #1 construct_match_selected_string at proto.c:6906 : #2 proto_can_match_selected at proto.c:7130 : #3 set_menus_for_selected_tree_row at main_menubar.c:5425 : #4 tree_view_selection_changed_cb at main.c:829 : #5 _g_closure_invoke_va at gclosure.c:840 : #8 _gtk_tree_selection_internal_select_node at gtktreeselection.c:1604 : #9 gtk_tree_view_real_set_cursor at gtktreeview.c:13208 : #10 gtk_tree_view_row_deleted at gtktreeview.c:9120 : #15 gtk_tree_model_row_deleted at gtktreemodel.c:1868
Created attachment 657482 [details] File: core_backtrace
Created attachment 657483 [details] File: environ
Created attachment 657484 [details] File: var_log_messages
Created attachment 657485 [details] File: limits
Created attachment 657486 [details] File: backtrace
Created attachment 657487 [details] File: cgroup
Created attachment 657488 [details] File: smolt_data
Created attachment 657489 [details] File: executable
Created attachment 657490 [details] File: dso_list
Created attachment 657491 [details] File: maps
Created attachment 657492 [details] File: proc_pid_status
Created attachment 657493 [details] File: build_ids
Created attachment 657494 [details] File: open_fds
Created attachment 663957 [details] My crash - probably the same issue - might have some useful...
I had done a live capture, and was lookin at the data, had just expanded one frame in the frame details "window", and switched to the next frame, then when I clicked the [+] sign to expand some of the data for the frame it crashed. This was while I was using unsaved data. backtrace_rating: 4 Package: wireshark-gnome-1.8.4-1.fc18 OS Release: Fedora release 18 (Spherical Cow)
Created attachment 670039 [details] Backtrace from attached GDB I think I've just hit by this as well. This can be easily triggered by opening a dump (sorry, can't submit), expanding some records, and hitting "close".
Crash on exit wireshark, after open dump file backtrace_rating: 4 cmdline: wireshark crash_function: strlen executable: /usr/sbin/wireshark kernel: 3.7.6-201.fc18.x86_64 package: wireshark-gnome-1.8.5-2.fc18 reason: Process /usr/sbin/wireshark was killed by signal 11 (SIGSEGV) remote_result: NOTFOUND uid: 1000
start wireshark, getent hosts irc.freenode.net (get IPv6 results), getent ahostsv4 irc.freenode.net, stop wireshark, expand DNS queries/answers, attempt to expand UDP frame, crash! backtrace_rating: 4 Package: wireshark-gnome-1.8.5-2.fc18 OS Release: Fedora release 18 (Spherical Cow)
Have been using wireshark-gnome-1.8.5-2.fc18.x86_64 for some time now and do not see the same symptoms any more (i.e. no more reproducible save crash and generally works just fine). I tried to reproduce the problems that you (others with bugs on this version) still seem to have but I couldn't.
Stable branch 1.8.x of the Wireshark is not gtk3 ready, so it was reverted back to use gtk2 gui library.