Possible memory leaks due to SuppressFinalize in constructors
-------------------------------------------------------------
Key: DNET-229
URL: http://tracker.firebirdsql.org/browse/DNET-229
Project: .NET Data provider
Issue Type: Bug
Components: ADO.NET Provider
Affects Versions: 2.5.0 Beta 2, 2.5.0 Beta 1, 2.5.0 Alpha 2, 2.5.0 Alpha 1,
2.1.0
Environment: Any
Reporter: Michał Ziemski
Assignee: Jiri Cincura
Using SuppressFinalize in class constructors is IMHO erroneous.
This causes Finalizers never to get called.
Classes embracing managed components should rather implement proper
Dispose/Finalize logic.
Expampe:
FbConnection con = new FbConnection(cStr);
con.Open();
con = null;
The underlying socket will not be closed because the Finalizer in
FbConnectionInternal will never be called.
SuppressFinalize is even sometimes called on classes that have no Finalizer
(for example GdsConnection).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Firebird-net-provider mailing list
Firebird-net-provider@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
