[issue3369] memory leak in floatobject.c

Mark Dickinson <[EMAIL PROTECTED]> added the comment: Fixed in r65179. I modified the patch slightly to include the "infinity" check, and to change "if(s_buffer)" to the slightly more explicit "if (s_buffer != NULL)". Thanks! -- resolution: -> fixed status: open -> closed _

[issue3369] memory leak in floatobject.c

Changes by Mark Dickinson <[EMAIL PROTECTED]>: -- assignee: -> marketdickinson ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bu

[issue3369] memory leak in floatobject.c

Mark Dickinson <[EMAIL PROTECTED]> added the comment: > Does this also apply to 2.6? Looks like it doesn't. :-). The patch needs to touch the newly arrived comparison with "infinity", as well as the "inf" and "nan" comparisons. ___ Python tracker <[EMAIL PR

[issue3369] memory leak in floatobject.c

Mark Dickinson <[EMAIL PROTECTED]> added the comment: Does this also apply to 2.6? -- nosy: +marketdickinson ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3369] memory leak in floatobject.c

Changes by Brett Cannon <[EMAIL PROTECTED]>: -- priority: -> normal ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mai

[issue3369] memory leak in floatobject.c

Changes by Brett Cannon <[EMAIL PROTECTED]>: -- nosy: +brett.cannon ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mail

[issue3369] memory leak in floatobject.c

Changes by Kristján Valur Jónsson <[EMAIL PROTECTED]>: -- type: -> resource usage ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python

[issue3369] memory leak in floatobject.c

New submission from Kristján Valur Jónsson <[EMAIL PROTECTED]>: When a nan or inf is generated in PyFloat_FromString(), a temporary buffer may be left behind. Patch attached. Found using Purify -- components: Interpreter Core files: tmp4.patch keywords: easy, patch, patch messages: 6972