Red Hat Bugzilla – Bug 157166
Python script causing memory leaks of over 1gb
Last modified: 2007-11-30 17:11:05 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.7) Gecko/20050520 Epiphany/1.6.2
Description of problem:
The attatched script, which is designed to convert UTF-8 into ISO-2022-JP, and back again in selected channels of xchat so that other channels can remain in utf-8 encoding whilst only one or two channels use japanese ISO-2022-JP encoding, causes a memory leak.
The code works perfectly fine on my FreeBSD installation, however on fedora core 3 it causes xchat to crash. I've had the code tested by two other people who are using FC3, and they reported the same problem.
Version-Release number of selected component (if applicable):
VERSION xchat 2.4.0 Linux 2.6.11-1.14_FC3 [i686/2.08GHz]
Steps to Reproduce:
1.Load the python script (ensuring that xchat's python module is loaded as well)
2.type "/jachan on" to enable iso-2022-jp conversion in the current channel
3.have someone message you something in japanese (in iso-2022-jp encoding of course)
Actual Results: the cpu usage maxes out, and memory consumption goes to the user oom (2gb) before crashing
Expected Results: proper conversion between iso-2022-jp and utf8
Created attachment 114138 [details]
The script causes endless recursion in decode() and xchat.emit_print().
system-install-packages -> userhelper -> python
Running open rpm with install invariably means a quick loss of all available
memory and the slow down of the PC as swapping begins.
The memory loss is attributable to Python taking up to 1GB.
I have an AMD 1200 Athlon, c/w 1GB of DDR 2100 on an ECS K7S5A.
I'm using FC4 development with the latest kernel
It happens consistently over multiple updates.
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
No feedback for months.