[Mono-devel-list] [Patch] the bug 61671 - OdbcExecuteNonQuery bug
sUmadevi at novell.com
Wed Jul 28 05:53:46 EDT 2004
The patch looks ok, please check it in.
>>> "T Sureshkumar" <tsureshkumar at novell.com> 7/27/2004 4:55:50 PM >>>
I have done a patch to bugzilla id 61671 (see description below).
attached file 61671.patch is the patch file & the memtest.cs is the
program. To check the mem leak, run the memtest.exe after compiling &
run "top" in another window. Make sure no other program is leaking
My patch also has one more change which eliminates of a redundant
function GetSQLState which I added during my previous patches.
please suggest if any changes need to be done.
Description of Problem:
OdbcCommand.ExecuteNonQuery is leaking.
I executed a simple program that inserts rows in a table (one-by-one)
using OdbcCommand.ExecuteNonQuery and I had the following error after
GLib-ERROR **: gmem.c:140: failed to allocate 8192 bytes
Using "top", I saw that "mono" had allocated 1Gb of memory...
Steps to reproduce the problem:
1. Execute the following program while monitoring memory usage of
static void Main(string args)
using(IDbConnection dbConnection = new
DSN NAME HERE>;UID=<ADD USER NAME HERE>;PWD=<ADD PASSWORD HERE>";
static void MyMethod(IDbConnection dbConnection)
IDbCommand dbCommand =
dbCommand.CommandText = "Set rowcount
Crash of mono.
How often does this happen?
More information about the Mono-devel-list