Bug #23981 memory leaks from yassl code + other

Submitted:	5 Nov 2006 8:59	Modified:	10 Nov 2006 20:42
Reporter:	Magnus Blåudd	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: General	Severity:	S1 (Critical)
Version:	5.0 + 5.1	OS:
Assigned to:	Magnus Blåudd	CPU Architecture:	Any

Description:
Memory leaks were detected by valgrind after push from -maint trees to 5.0 and 5.1

How to repeat:
Run with valgrind

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/14965

ChangeSet@1.2290, 2006-11-07 15:20:24+01:00, msvensson@neptunus.(none) +1 -0
  Bug#23981 memory leaks from yassl code + other
   - Fix memory leak in vio_VioSSLFD that occurs when one of the calls to SSL_* function fails. As in the "ssl_des"
     test case where the server is currently not supposed to be able to read the specific cert/key file.
   - Change error message to be generic as it's called both from server and client code.

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/14968

ChangeSet@1.2548, 2006-11-07 16:09:32+01:00, msvensson@neptunus.(none) +1 -0
  Bug#23981 memory leaks from yassl code + other
   - Readd --skip-bdb when valgrinding

Noted in 5.0.30, 5.1.13 changelogs.

Some yaSSL-related memory leaks detected by Valgrind were fixed.

Page generated in 0.059 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.