[Winpcap-users] WinPcap 3.1 beta 4 memory leak? crashes?

Le anh Dung dungbkhn at yahoo.com
Wed May 25 01:15:07 GMT 2005


So do I, i'm watting and using temporary solution. I found this error in function:

PacketGetAdapterNames(PTSTR pStr,PULONG BufferSize) in packet.dll project
in source code, but it's difficult to repaire.

Thanks Mr Gianluca!

Tom Brown <brown at esteem.com> wrote:
Gianluca,

Thank you! That explains what we are seeing. How long is a few weeks? Two 
weeks? Three weeks? My manager would like you to know we are calling 
pcap_findalldevs() in a "mission critical" application. It's already been 
released to our customers and we are looking for an update soon. In the 
meantime, I can try using RegisterDeviceNotification(), as suggested in a 
previous post, to cut down on the memory leakage.

Thanks,
Tom

On Sunday 22 May 2005 09:51, Gianluca Varenni wrote:
> Hi Tom.
>
> I can confirm that there are some memory leaks affecting pcap_findalldevs
> (down deep in the packet.dll APIs), that have been already fixed on our
> source tree.
>
> They will be available in the upcoming winpcap 3.1, which we plan to ship
> in few weeks.
>
> Have a nice day
> GV
>
> ----- Original Message -----
> From: "Tom Brown" 

> To: 
> Sent: Saturday, May 21, 2005 12:51 PM
> Subject: [Winpcap-users] WinPcap 3.1 beta 4 memory leak? crashes?
>
> >I have a Delphi application using the WinPcap library. The application
> >polls a
> > device on the ethernet port every second for status information. The
> > application will poll for a device every half second if it can't find one
> > right away. The crashes and memory leak seem to occur when the etherenet
> > cable pulled. The application will slowly leak memory and sometimes
> > crashes
> > after a few seconds or a few hours of operation.
> >
> > It appears the calls into the WinPcap library is the problem. When I take
> > out
> > the calls into the WinPcap library the application runs without memory
> > leaks
> > and does not crash. Of course, it isn't doing a whole lot at this point
> > either. I searched google and the mailing list and did not find any
> > memory leak issues with WinPcap 3.1 beta 4. Are there any issues with
> > calling pcap_findalldevs() every half second? Any ideas?
> >
> > Thanks,
> > Tom
> > _______________________________________________
> > Winpcap-users mailing list
> > Winpcap-users at winpcap.org
> > https://www.winpcap.org/mailman/listinfo/winpcap-users
>
> _______________________________________________
> Winpcap-users mailing list
> Winpcap-users at winpcap.org
> https://www.winpcap.org/mailman/listinfo/winpcap-users

_______________________________________________
Winpcap-users mailing list
Winpcap-users at winpcap.org
https://www.winpcap.org/mailman/listinfo/winpcap-users

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.winpcap.org/pipermail/winpcap-users/attachments/20050524/6e4fa0b1/attachment.html


More information about the Winpcap-users mailing list