| Bug ID |
12044
|
| Summary |
Selecting packets causes memory leak
|
| Product |
Wireshark
|
| Version |
2.0.1
|
| Hardware |
x86
|
| OS |
Mac OS X 10.11
|
| Status |
CONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Qt UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Version 2.0.1 (v2.0.1-0-g59ea380 from master-2.0)
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) i7-4790K CPU @ 4.00GHz (with SSE4.2)
Built using llvm-gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM build
2336.9.00).
--
1) start capture on any interface, capture at least two packets.
2) select another packet, memory use increases by ~4 MB
I have had crashes that are logged. I'm unwilling to attempt reproducing a
crash because swap usage slows down my system, and I suspect.
The 32-bit version has a similar behavior to a lesser extent, memory usage
increases by about 200 KB per selection.
Bug appears identical to
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7775.
You are receiving this mail because:
- You are watching all bug changes.