On May 10, 2011, at 8:28 AM, Keyoor Khristi wrote:

> for some reason the rt.openssl.org site is asking me for username/password. 
> But 
You can use guest/guest...

Best regards
Michael
> i've the email from rt on behalf of rt. we didnt add another clear_queue 
> function. we just cleared the DTLS RECORD from the while loop and it worked.
It would be nice to know the the fix which works for us also works for you...

Best regards
Michael
> 
> 
> On Mon, May 9, 2011 at 7:56 PM, Michael Tüxen 
> <[email protected]> wrote:
> On May 5, 2011, at 2:22 PM, Keyoor Khristi wrote:
> 
> > I just now realized that there is already a ticket 
> > http://rt.openssl.org/Ticket/Display.html?id=1714 for this issue.
> > It would be helpful to know anything more about this ticket or issue.
> Hi Keyoor,
> 
> does the *updated* patch provided by Robin in
> http://rt.openssl.org/Ticket/Display.html?id=2506
> fix your problem?
> 
> Best regards
> Michael
> >
> > Regards,
> > Keyoor
> >
> >
> > On Thu, May 5, 2011 at 2:58 PM, Keyoor Khristi <[email protected]> 
> > wrote:
> > Hi All,
> >
> > I'm facing a problem of memory leak and the symptoms lead to dtls1_free.
> > We are getting many packets which are in next epoch. they get buffered in 
> > unprocessed records queue in dtls1_buffer_record function. in this function 
> > the s->s3->rbuf is shallow copied to rdata->rbuf. later s->s3->rbuf is set 
> > to zero. so, the pointer to the record data is in rdata->rbuf which is an 
> > item in the queue. The dtls1_free takes out each item from the queue and 
> > frees the item->data. but the original records are pointed by 
> > item->data->rbuf structure. these are not getting freed.
> > I looked in latest openssl 1.0.0 and the same problem is there too.
> > please let me know if it is really a problem in dtls1_free or we're missing 
> > something.
> >
> > Regards,
> > Keyoor
> >
> >
> 
> 

______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [email protected]
Automated List Manager                           [email protected]

Reply via email to