assertion when using tshark/wireshark on large captures

["Bahr, Brad (Adecco Engineering & Technical)" <brad.bahr () hp com>]

I am running the 64bit version of Wireshark/tshark (v1.4.3 rev35482 - compiled download) on a 64bit Windows 7 box.  
When I am applying read filters to large captures (1.5GB+) with tshark, I get this assertion:

ERROR:emem.c:652:???: assertion failed: (ret != 0 || versinfo.dwPlatformId == VER_PLATFORM_WIN32_WINDOWS)

Also in stderr are numerous warnings about dissector bugs with the SMB2 and VNC protocols.  I'm not sure if these are 
related but thought they would be worth mentioning.  From a cursory glance at the source heading of emem.c, I gather 
that this file provides memory management / garbage cleanup functions.  I'm definitely a novice when it comes to C/C++, 
so I don't have a clue as to what would be causing g_assert to be getting a false from "ret != 0 || 
versinfo.dwPlatformId == VER_PLATFORM_WIN32_WINDOWS".

If I try to open this same capture file with Wireshark, it also dies a terrible death before the capture is loaded.  
Both tshark and Wireshark seem to be croaking when they have consumed about 2GB of memory, which makes me wonder if its 
related to some 32bit snafu.  My box has dual quad xeons and 12GB of ram, so hardware is likely not a concern.  Any 
ideas??

Thanks,
Brad

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request () wireshark org?subject=unsubscribe