Re: Fwd: bug 11723

[Anirudh Agarwal <agarwal.anirudh98 () gmail com>]

Hi,
I am already working on the latest developer build cross checked with the
command "git status" and version displaying from the " help -> about
wireshark " is developer version 3.3.0.


On Thu, 12 Mar 2020 at 16:46, Jirka Novak <j.novak () netsystem cz> wrote:

> Hi,
>
> >     > While I was exploring the bug
> >     > https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11723
> >     >
> >     > i encountered the RTP player was not able to play the audio even
> after
> >     > re-opening it again and again. After reaching the state as shown
> >     in the
> >     > screenshot, I clicked the play button but nothing happened. Am I
> doing
> >     > something wrong or is it the bug which needs to be resolved.
> >
> >     If you scroll a bit to the right in the initial dialog (or resize the
> >     window), can you see "22" in the Packets column? Following the steps
> in
> >     Bug 11723, opening the VoIP calls dialog initially shows "11". When I
> >     press "Play Streams", the contents will only appear once the column
> >     reaches "22".
> >
> >
> > okay, I got this. The value of the packet switches to 22 from 11, and so
> on.
> >     If I close the RTP Player dialog again, and press "Play Streams"
> again,
> >     then the contents will be empty. I have not investigated why this
> >     happens, but it might be related to some state in the dialog not
> being
> >     cleared when the "tap" mechanism[1] used by the RTP player passed
> >     through it. That could also explain the 11 -> 22 -> 33 -> ... Packets
> >     bug. And yes, it is an open bug, feel free to investigate it and
> submit
> >     a patch for it. :-)
>
> It looks like issue I fixed some time ago in master branch. Try latest
> developer build for master if you still see it.
> BTW I hope I fixed the issue with "Warn remove_tap_listener(): no
> listener found with that tap data" mentioned in the bug too.
>
>                                                         Jirka Novak
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe