Re: WARNING **: Too many taps queued

[Martin Mathieson <martin.r.mathieson () googlemail com>]

On Wed, Oct 10, 2012 at 9:41 PM, Jaap Keuter <jaap.keuter () xs4all nl> wrote:

> On 10/10/2012 03:48 PM, mmann78 () netscape net wrote:
>
> > I ran some fuzztesting overnight (on a 32-bit WinXP VM, off of trunk),
> > and when
> > I checked on it this morning, I had "WARNING **: Too many taps queued" so
> > many
> > times, it scrolled beyond the top of my window.
> >
> > I've never seen this before. Could it be a result of the files I was
> > testing?
> > New bug in the trunk?
> >
> > Any insight would be appreciated.
> Your fuzz probably triggered a loop over a tapping point. There can be
> TAP_PACKET_QUEUE_LEN (=100) taps be pushed per packet.
>
> You should grab that fuzz and investigate the loop.
>
> Thanks,
> Jaap
I get it all the time.  After convincing myself I wasn't losing any tap
events I have been ignoring it.  Would be interested to know what it
meant...

Martin

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe