<DIV>So do I, i'm watting and using temporary solution. I found this error in function<FONT color=#880000 size=2>:</DIV>
<P>PacketGetAdapterNames</FONT><FONT size=2>(</FONT><FONT color=#0000ff size=2>PTSTR</FONT><FONT size=2> </FONT><FONT color=#808080 size=2>pStr</FONT><FONT size=2>,</FONT><FONT color=#0000ff size=2>PULONG</FONT><FONT size=2> </FONT><FONT color=#808080 size=2>BufferSize</FONT><FONT size=2>) in packet.dll project</P>
<DIV></FONT>in source code, but it's difficult to repaire.<BR></DIV>
<DIV>Thanks Mr Gianluca!</DIV>
<DIV><BR><B><I>Tom Brown <brown@esteem.com></I></B> wrote:</DIV>
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Gianluca,<BR><BR>Thank you! That explains what we are seeing. How long is a few weeks? Two <BR>weeks? Three weeks? My manager would like you to know we are calling <BR>pcap_findalldevs() in a "mission critical" application. It's already been <BR>released to our customers and we are looking for an update soon. In the <BR>meantime, I can try using RegisterDeviceNotification(), as suggested in a <BR>previous post, to cut down on the memory leakage.<BR><BR>Thanks,<BR>Tom<BR><BR>On Sunday 22 May 2005 09:51, Gianluca Varenni wrote:<BR>> Hi Tom.<BR>><BR>> I can confirm that there are some memory leaks affecting pcap_findalldevs<BR>> (down deep in the packet.dll APIs), that have been already fixed on our<BR>> source tree.<BR>><BR>> They will be available in the upcoming winpcap 3.1, which we plan to ship<BR>> in few weeks.<BR>><BR>> Have a nice day<BR>>
GV<BR>><BR>> ----- Original Message -----<BR>> From: "Tom Brown" <BROWN@ESTEEM.COM><BR>> To: <WINPCAP-USERS@WINPCAP.ORG><BR>> Sent: Saturday, May 21, 2005 12:51 PM<BR>> Subject: [Winpcap-users] WinPcap 3.1 beta 4 memory leak? crashes?<BR>><BR>> >I have a Delphi application using the WinPcap library. The application<BR>> >polls a<BR>> > device on the ethernet port every second for status information. The<BR>> > application will poll for a device every half second if it can't find one<BR>> > right away. The crashes and memory leak seem to occur when the etherenet<BR>> > cable pulled. The application will slowly leak memory and sometimes<BR>> > crashes<BR>> > after a few seconds or a few hours of operation.<BR>> ><BR>> > It appears the calls into the WinPcap library is the problem. When I take<BR>> > out<BR>> > the calls into the WinPcap library the application runs without memory<BR>> >
leaks<BR>> > and does not crash. Of course, it isn't doing a whole lot at this point<BR>> > either. I searched google and the mailing list and did not find any<BR>> > memory leak issues with WinPcap 3.1 beta 4. Are there any issues with<BR>> > calling pcap_findalldevs() every half second? Any ideas?<BR>> ><BR>> > Thanks,<BR>> > Tom<BR>> > _______________________________________________<BR>> > Winpcap-users mailing list<BR>> > Winpcap-users@winpcap.org<BR>> > https://www.winpcap.org/mailman/listinfo/winpcap-users<BR>><BR>> _______________________________________________<BR>> Winpcap-users mailing list<BR>> Winpcap-users@winpcap.org<BR>> https://www.winpcap.org/mailman/listinfo/winpcap-users<BR><BR>_______________________________________________<BR>Winpcap-users mailing
list<BR>Winpcap-users@winpcap.org<BR>https://www.winpcap.org/mailman/listinfo/winpcap-users<BR></BLOCKQUOTE><p>__________________________________________________<br>Do You Yahoo!?<br>Tired of spam? Yahoo! Mail has the best spam protection around <br>http://mail.yahoo.com