| Bug ID |
8102
|
| Summary |
Possible memory leak in packet-synphasor
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
SVN
|
| Hardware |
All
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Wireshark
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
TShark 1.9.0 (SVN Rev 46576 from /trunk)
Copyright 1998-2012 Gerald Combs <[email protected]> and contributors.
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 GLib 2.34.3, with libpcap, with libz 1.2.7, with POSIX
capabilities (Linux), without libnl, with SMI 0.4.8, with c-ares 1.9.1, with
Lua
5.2, without Python, with GnuTLS 2.12.20, with Gcrypt 1.5.0, with MIT Kerberos,
with GeoIP.
Running on Linux 3.7.0-7-generic, with locale en_CA.UTF-8, with libpcap version
1.3.0, with libz 1.2.7.
Built using gcc 4.7.2.
--
As discovered in bug #8089 by code review when someone copied it for use in
their own dissector.
Should only occur in the case of a seriously malformed packet, in
config_frame_fast() if one of the tvb_ functions throws an exception after
g_array_new() is called. It should probably just use file-scoped wmem memory.
You are receiving this mail because:
- You are watching all bug changes.
