https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5549
--- Comment #3 from Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> 2011-05-23 14:08:26 PDT ---
(In reply to comment #2)
> (In reply to comment #1)
> > Be sure to read the workarounds listed in bug 3046.
> >
> > *** This bug has been marked as a duplicate of bug 3046 ***
>
> Thanks,
>
> Please be aware that I had looked at bug 3046 before creating a new bug report
> and decided it did not apply in my case.
>
> I never get a hung "Closing File!" dialog, and Wireshark is snoozing along at
> about 75% CPU (reported by Sysinternals Process Explorer on XP).
Are you the originator of this bug (e.g., new email address)? I ask because
comment 0 specifically says:
: "The "Closing File! Please wait..." popup occurs every time a file is
closed.
which matches bug 3046.
> Please help me understand the work-around. My goal is a workable two-stage
> filter; 1st stage lipcap "ip proto 0x2f" and the second stage any valid display
> filter. I'm not sure how to use dumpcap to accomplish this.
Do you mean these workarounds?
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3046#c5
I'm not sure what else to say than what Jim described.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
