U misunderstood me.. I meant that I didn't expect Wireshark to have this issue and eat upmemory - not what it threw up in error.
BTW - it did lock up my machine when running 1.0.7 - I only got the error with 1.0.5
-----Original Message-----
From: wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of Guy Harris
Sent: Wednesday, April 22, 2009 2:47 PM
To: Community support list for Wireshark
Subject: Re: [Wireshark-users] 700 Meg File Wireshark 1.0.7 - Wireshark hangs
On Apr 22, 2009, at 11:26 AM, Ujjval Karihaloo wrote:
> Any case Wireshark should not give this error even if its Windows -
> Out OF memory
What would you suggest it do if it runs out of memory? Crash? Not
tell the user?
The fact that it exits is unfortunate; it would be better if, were you
to try to read a file that's too large, it closes the file, frees all
the memory it allocated while reading the file, and then pops up a
dialog box saying that it ran out of memory.
It would also be nice if it used less memory, so that the upper limit
on the size of the file it could read would be higher; there are a
number of ideas about how to do that, but not all of them are simple.
___________________________________________________________________________
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
