[issue3153] sqlite leaks on error

2008-07-13 Thread Alexandre Vassalotti

Alexandre Vassalotti [EMAIL PROTECTED] added the comment:

Fixed in r64930 (trunk) and r64931 (py3k). Thanks.

--
nosy: +alexandre.vassalotti
resolution:  - fixed
status: open - closed

___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3153
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue3153] sqlite leaks on error

2008-06-20 Thread Adam Olsen

New submission from Adam Olsen [EMAIL PROTECTED]:

Found in Modules/_sqlite/cursor.c:

self-statement = PyObject_New(pysqlite_Statement,
pysqlite_StatementTy
pe);
if (!self-statement) {
goto error;
}
rc = pysqlite_statement_create(self-statement,
self-connection, operation);
if (rc != SQLITE_OK) {
self-statement = 0;
goto error;
}

Besides the ugliness of allocating the object before passing it to the
create function, if pysqlite_statement_create fails, the object is leaked.

--
components: Extension Modules
messages: 68478
nosy: Rhamphoryncus
severity: normal
status: open
title: sqlite leaks on error
type: resource usage

___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3153
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com