ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
July 17th, 2024 | 10:00am-11:55am SGT (UTC+8) | Online

Wireshark-bugs: [Wireshark-bugs] [Bug 12166] New: RTP audio player crashes

Date: Wed, 24 Feb 2016 17:48:10 +0000
Bug ID 12166
Summary RTP audio player crashes
Product Wireshark
Version 2.0.1
Hardware x86
OS Mac OS X 10.11
Status UNCONFIRMED
Severity Major
Priority Low
Component GTK+ UI
Assignee [email protected]
Reporter [email protected]

Created attachment 14356 [details]
no ringback

Build Information:
Version 2.0.1 (v2.0.1-0-g59ea380 from master-2.0)

Copyright 1998-2015 Gerald Combs <[email protected]> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with Qt 5.3.2, with libpcap, without POSIX capabilities, with
libz 1.2.5, with GLib 2.36.0, with SMI 0.4.8, without c-ares, without ADNS,
with
Lua 5.2, with GnuTLS 2.12.19, with Gcrypt 1.5.0, with MIT Kerberos, with GeoIP,
with QtMultimedia, without AirPcap.

Running on Mac OS X 10.11.3, build 15D21 (Darwin 15.3.0), with locale C, with
libpcap version 1.5.3 - Apple version 54, with libz 1.2.5, with GnuTLS 2.12.19,
with Gcrypt 1.5.0.
Intel(R) Core(TM)2 Extreme CPU X7900  @ 2.80GHz

Built using llvm-gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM build
2336.9.00).
--
Hi, 

I have the same issue as #10613
(https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10613) - But instead of
being with Wireshark 1.12.1 , the issue is with Wireshark 2.0.1

Scenario:
- A sip call is made between a device and IP PBX. 
- A wireshark trace is being ran on a mirrored port. 

When I open the wireshark trace on my OS X , everything is fine. 
Until I select a SIP frame then Telephony / VOIP CALL / Play Stream / PLAY

-> As soon as the audio ends, OR I hit the STOP button, wireshark crashes. 

I attached the trace that I use as an example.


You are receiving this mail because:
  • You are watching all bug changes.