[issue8065] Memory leak in readline.get_current_history_length

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 ca

[issue8065] Memory leak in readline.get_current_history_length

Changes by Ezio Melotti : -- versions: -Python 3.1 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue8065] Memory leak in readline.get_current_history_length

Garrett Cooper 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: http://www.netbsd.org/cgi-bin/sendpr.cgi?

[issue8065] Memory leak in readline.get_current_history_length

Antoine Pitrou 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: http://www.python.org/dev/buildbot/al

[issue8065] Memory leak in readline.get_current_history_length

Mark Dickinson 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 clear whether libedit k

[issue8065] Memory leak in readline.get_current_history_length

Mark Dickinson added the comment: See also issue 9450 (leaks in readline.replace_history_item and readline.remove_history_item). -- nosy: +mark.dickinson ___ Python tracker ___

[issue8065] Memory leak in readline.get_current_history_length

Alexander Belopolsky 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 Bug 09-Mar-2010 05:39 PM Open --

[issue8065] Memory leak in readline.get_current_history_length

Ronald Oussoren 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 be fixed, but you neve

[issue8065] Memory leak in readline.get_current_history_length

Changes by Ronald Oussoren : Removed file: http://bugs.python.org/file16480/smime.p7s ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue8065] Memory leak in readline.get_current_history_length

Alexander Belopolsky 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 libedit is NetBSD, http://cvsweb

[issue8065] Memory leak in readline.get_current_history_length

Changes by Zvezdan Petkovic : -- nosy: +zvezdan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue8065] Memory leak in readline.get_current_history_length

Ronald Oussoren 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: http://bugs.python.org/file16480/s

[issue8065] Memory leak in readline.get_current_history_length

Alexander Belopolsky 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 the history cookie ("_HiStOrY_V2

[issue8065] Memory leak in readline.get_current_history_length

Alexander Belopolsky 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 writing history files. Also, I fin

[issue8065] Memory leak in readline.get_current_history_length

Alexander Belopolsky 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 time history_get_history_state