Comment # 1
on bug 10068
from Guy Harris
Is there a file that's large enough to consume a lot of memory but not so large
as to consume so much memory to render the machine unusable?
If so, could you hack tshark.c to put an infinite loop at the end of main():
@@ -2212,6 +2212,9 @@ main(int argc, char *argv[])
output_fields_free(output_fields);
output_fields = NULL;
+for (;;)
+pause();
+
return exit_status;
}
rebuild tshark, run it on the file in question with
MallocStackLogging=1 tshark {args}
and then, after it prints the statistics, run "leaks" on the tshark process?
(I tried that on some simple files, and the Mavericks version "leaked" *less*
memory than the Mountain Lion version, but the "leaks" are probably allocations
to store data from files read in during the startup process, e.g. SNMP MIB
files. There's something else going on in your case.)
You are receiving this mail because:
- You are watching all bug changes.
