[issue8065] Memory leak in readline.get_current_history_length

2014-10-08 Thread Terry J. Reedy
Terry J. Reedy added the comment: The leak had been fixed in #9450. There are still the remaining issues of: - better testing for the readline module, and - attempting to work around libedit bugs. Perhaps those should become separate issues, though? If those are current issues and anyone

[issue8065] Memory leak in readline.get_current_history_length

2011-11-28 Thread Ezio Melotti
Changes by Ezio Melotti ezio.melo...@gmail.com: -- versions: -Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8065 ___ ___

[issue8065] Memory leak in readline.get_current_history_length

2011-10-10 Thread Garrett Cooper
Garrett Cooper yaneg...@gmail.com added the comment: As a note for future reference, FreeBSD/NetBSD/OpenBSD doesn't use the term bug, but instead uses the term problem report (the NetBSD website says bug though BTW). The PR system for NetBSD can be accessed here:

[issue8065] Memory leak in readline.get_current_history_length

2011-04-24 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr added the comment: For the record, I tried Alexander's tests on the buildbots and it failed on OS X Leopard: http://www.python.org/dev/buildbot/all/builders/AMD64%20Leopard%20custom/builds/12/steps/test/logs/stdio but succeeded on OS X Tiger:

[issue8065] Memory leak in readline.get_current_history_length

2010-08-03 Thread Mark Dickinson
Mark Dickinson dicki...@gmail.com added the comment: I've fixed this leak in r83670 through r83672. It's still using the old, inefficient method (get the state, read the length, free the state), because without good tests I don't want to disturb things too much. In particular, it's not

[issue8065] Memory leak in readline.get_current_history_length

2010-08-01 Thread Mark Dickinson
Mark Dickinson dicki...@gmail.com added the comment: See also issue 9450 (leaks in readline.replace_history_item and readline.remove_history_item). -- nosy: +mark.dickinson ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8065

[issue8065] Memory leak in readline.get_current_history_length

2010-03-09 Thread Alexander Belopolsky
Alexander Belopolsky alexander.belopol...@gmail.com added the comment: I my experience, reporting bugs in open source components of OSX to bugreport.apple.com is a waste of time. Such reports are largely ignored and they are not visible to upstream developers. I believe the upstream for

[issue8065] Memory leak in readline.get_current_history_length

2010-03-09 Thread Ronald Oussoren
Changes by Ronald Oussoren ronaldousso...@mac.com: Removed file: http://bugs.python.org/file16480/smime.p7s ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8065 ___

[issue8065] Memory leak in readline.get_current_history_length

2010-03-09 Thread Ronald Oussoren
Ronald Oussoren ronaldousso...@mac.com added the comment: Without filing a bug Apple won't know that something is wrong and they will definitly not fix the issue. If you file an issue and post the radar number I'll ping the Python maintainer inside Apple. There's little change that this will

[issue8065] Memory leak in readline.get_current_history_length

2010-03-09 Thread Alexander Belopolsky
Alexander Belopolsky alexander.belopol...@gmail.com added the comment: I submitted two bug reports: 7734961 libedit history_truncate_file () fails to preserve magic line Mac OS X Other Bug 09-Mar-2010 05:48 PM Open 7734839 libedit read_history() does not update history_length Mac OS X Other

[issue8065] Memory leak in readline.get_current_history_length

2010-03-08 Thread Zvezdan Petkovic
Changes by Zvezdan Petkovic zvez...@zope.com: -- nosy: +zvezdan ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8065 ___ ___ Python-bugs-list

[issue8065] Memory leak in readline.get_current_history_length

2010-03-06 Thread Alexander Belopolsky
Alexander Belopolsky alexander.belopol...@gmail.com added the comment: It appears that the tests that I attached fail when libedit is used. This is clearly due to bugs in libedits readline emulation: 1. read_history does not update history_length 2. history_truncate_file does not preserver

[issue8065] Memory leak in readline.get_current_history_length

2010-03-06 Thread Ronald Oussoren
Ronald Oussoren ronaldousso...@mac.com added the comment: On 7 Mar, 2010, at 1:02, Alexander Belopolsky wrote: Does anyone know where libedit bugs should be reported? Apple's bugreporter. (bugreport.apple.com, you need an ADC account to report bugs). -- Added file:

[issue8065] Memory leak in readline.get_current_history_length

2010-03-05 Thread Alexander Belopolsky
Alexander Belopolsky alexander.belopol...@gmail.com added the comment: Note the following comment elsewhere in Modules/readline.c: /* the history docs don't say so, but the address of state changes each

[issue8065] Memory leak in readline.get_current_history_length

2010-03-05 Thread Alexander Belopolsky
Alexander Belopolsky alexander.belopol...@gmail.com added the comment: Not directly related to the issue at hand, but I've noticed that while readline.get_current_history_length() is tested in the unittests, readline.get_history_length() is not. Attached patch adds tests for reading and