Bug 217378

I think there is a pretty bad memory leak, probably related to scrollback
buffering or terminal output.  I usually have quite a few terminals open, and
after a day or two my swap is completely exhausted, eventually causing
gnome-terminal to crash.

Here's my 'ps' output:

jim      12629  0.3 22.2 654176 230092 ?       Sl   Dec04  14:19 gnome-terminal

The numbers hold steady if there is no terminal output.  After doing an 'ls -lR'
in a fairly large source directory, I get:

jim      12629  0.3 27.8 654176 288272 ?       Sl   Dec04  14:52 gnome-terminal

I just installed F7 test2 and updated to rawhide and now gnome-terminal crashes
on startup for me.  How do we go about debugging this?

Bah, sorry for the noise.  I think our problems are different (and I'm not on
x86_64).

I'm not on x86_64, but I think that my problem is the same.

I have 2 FC6 machines here (one x86_64, one x86) - after a recent update I find
ctrl+shift+N sometimes causes all my gnome terms to crash.

I'm running gnome-terminal-2.16.0-2.fc6 under Beryl.  My .xsession-errors shows:


The program 'gnome-terminal' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 39083 error_code 8 request_code 62 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)


I understand the arguements for using a single process to run all the windows,
but it's a really bad thing to see 20 terminal windows all explode at the same
time (especially since they explode in a ball of flames thanks to Beryl's fire
effect :)

can you do what the output asks you to do, and run 

gdb --args gnome-terminal --sync

and then report the resulting stacktrace, please ?

I am currently running my gnome terms in gdb.  However, the crashes are
infrequent so I may not be able to produce a stack dump any time soon.

This looks like it may be a different problem, but it still resulted in a crash.
 Unfortunately gdb hasn't produced any especially useful output:

(gdb) break gdk_x_error
Function "gdk_x_error" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y

Breakpoint 1 (gdk_x_error) pending.
(gdb) run
Starting program: /usr/bin/gnome-terminal --sync
[Thread debugging using libthread_db enabled]
[New Thread 46912496366048 (LWP 8895)]
[New Thread 1084229952 (LWP 8903)]
[New Thread 1094719808 (LWP 8997)]
[New Thread 1105209664 (LWP 8998)]
[Thread 1105209664 (LWP 8998) exited]
[Thread 1094719808 (LWP 8997) exited]
[New Thread 1094719808 (LWP 8999)]
[New Thread 1105209664 (LWP 9000)]
[Thread 1094719808 (LWP 8999) exited]
[Thread 1105209664 (LWP 9000) exited]

(gnome-terminal:8895): Vte-WARNING **: No handler for control sequence
`device-control-string' defined.
Couldn't get registers: No such process.
(gdb) bt
Couldn't get registers: No such process.
(gdb) 

Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.

If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we're following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

Not seen this happen in a recent Fedora.

Keeping this bug open doesn't seem very productive. I'm going to close it now.
If you witness a gnome-terminal crash in current releases, just file a new one,
please.