gnome-terminal keeps tabs in memory

[Michael Lustfield]

Binary package hint: gnome-terminal

I'm running Ubuntu 8.04. I regularly use gnome-terminal for a large majority of my terminal emulator usage.

If I open two tabs, start two tasks in each, such as copying 15GB which I occasionally do, then close that tab via the X, the tab is closed and can't be returned to - but the system resources are still being hogged up. I'm pretty sure that activity is still going on too.

This isn't usually much of an issue. However, in instances where the task is system intensive and keeps running, it is a problem.

Also, using the exit command does seem to kill the tab.

[Bhavani Shankar (bhavi)]

Thanks for your bug report.

go to file menu > close tab and try it out...

Regards

[Michael Lustfield (michaellustfield)]

Same thing still happens.

Here's how I test.

Open two tabs.
In tab #1, cp ~/test/15_GB_File ~/test/Another_File
In tab #2, watch du -h ~/test/*
Close tab #1

The watch will show you that the file is still growing.

I tried both methods of closing the terminal.

I know it's with gnome-terminal and not my laptop. I've seen this happen on other systems as well.

[Pedro Villavicencio (pedro)]

could this be a duplicate of bug 207477?

[Michael Lustfield (michaellustfield)]

This is not a duplicate of that bug.

It's still reproducible in 8.10. I no longer use gnome-terminal but it's easily reproduced. This is a potential huge memory leak and battery drain. This is the only reason I see it as a serious bug.

[Michael Lustfield (michaellustfield)]

I also think it should be considered for a security flag because a user could start working on data in one tab that has private data and another user could read that stream even after the tab is closed.

[Brian Murray (brian-murray)]

I've tried recreating your test case multiple times without success, every time I close the tab the process being executed is killed. I'm also really not clear why you confirmed the bug when you say "I no longer use gnome-terminal but it's easily reproduced." Please either elaborate on your test case, so someone else can try and recreate it, or test it again in Intrepid.

Also please take a moment to review http://wiki.ubuntu.com/Bugs/Status which indicates that 'Confirmed bugs require confirmation from someone other than the original reporter'.

[Michael Lustfield (michaellustfield)]

I'm sorry, I think I was working on too many bugs at once. I didn't mean to confirm this one.

I did try it again and it appears to have been taken care of.

Sorry for the hassle. I suppose a Fix Released or Invalid flag is more appropriate for this bug.

[Brian Murray (brian-murray)]

Invalid is the most appropriate status for this bug as there is no clear indication as what the fix for the bug report was. Thanks for following up!