Could it also relate to cap vs. pcap file? I tried 145KB .cap file and it ran fine but a 130KB .pcap file stalls tshark as well. In addition, these commands are done using Python and that's when the errors occurs. If I perform the commands from the command prompt, it runs fine.
From the desk of Nicole A. Powell.....
> From: guy@xxxxxxxxxxxx
> To: wireshark-users@xxxxxxxxxxxxx
> Date: Tue, 10 Nov 2009 09:24:23 -0800
> Subject: Re: [Wireshark-users] running multiple instances
>
>
> On Nov 9, 2009, at 1:21 PM, Nicole Powell wrote:
>
> > When I try this it gives an application error and shuts down Tshark.
> > I tried these two commands on a smaller file (144KB) and it works
> > fine; the file I am trying to use now is 4.59MB. Could it be the
> > file size?
>
> Yes, it could be. There are some cases where TShark keeps information
> around in memory even after it's no longer needed (because TShark and
> Wireshark use the same dissector code and dissector framework, and, in
> Wireshark, that information could be needed as long as the file is
> open), so it can use a significant amount of memory on a large file.
> ___________________________________________________________________________
> Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
> Archives: http://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
> mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe
|
