[Bug 138607] Re: gnome-terminal memory leak

2008-11-04 Thread Simetrical
Well, there already seem to be lots of bugs upstream, per my previous comments. Some of them suggest it should have been fixed some time ago, so maybe a fix got into Intrepid? -- gnome-terminal memory leak https://bugs.launchpad.net/bugs/138607 You received this bug notification because you are

[Bug 138607] Re: gnome-terminal memory leak

2008-07-16 Thread Simetrical
I did some hunting upstream. These bugs blame a bug in Xft on versions of X lacking RENDER support: http://bugzilla.gnome.org/show_bug.cgi?id=95023 http://bugzilla.gnome.org/show_bug.cgi?id=99255 http://bugzilla.gnome.org/show_bug.cgi?id=100269 http://bugzilla.gnome.org/show_bug.cgi?id=107911 Th

[Bug 138607] Re: gnome-terminal memory leak

2008-02-27 Thread Simetrical
That option was already off for me. I don't know if this is precisely the same issue, but I have observed that it seems to use an inordinate amount of memory. I previously had a maximum scrollback size of 10 lines, which works out to 62 MB per tab, but my memory usage went a lot over that aft

[Bug 138607] Re: gnome-terminal memory leak

2008-02-26 Thread Simetrical
1) Which accessibility options might these be? I'd be happy to disable them, but I can't find them. 2) Is this bug still supposed to be Incomplete? The requested information was attached. I've experienced this bug. I just realized gnome-terminal was using >500 MB of resident memory, and probab

[Bug 93847] Re: Excessive CPU usage by Gnome System Monitor

2007-09-24 Thread Simetrical
Opening top and gnome-system-monitor simultaneously (in Feisty), I can observe that top takes < 1% CPU, g-s-m takes 10-30% CPU. This isn't a misreporting issue unless it's at a lower level: as ld2ndR says, the two report similar results. The fact that top takes much less is also notable, in that