Bug 555061 - apps killed in gnome-terminal continue to run and go to 100% of cpu
Summary: apps killed in gnome-terminal continue to run and go to 100% of cpu
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-terminal
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Behdad Esfahbod
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-13 15:02 UTC by pleabargain
Modified: 2010-04-13 14:18 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-04-13 14:18:10 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description pleabargain 2010-01-13 15:02:32 UTC
[user@localhost ~]$ uname -r
2.6.31.9-174.fc12.i686
[user@localhost ~]$ rpm -qa gnome-terminal
gnome-terminal-2.28.2-1.fc12.i686




Description of problem:
Twice today I went to su.
I ran system-network-config
later one of my dual cores went to 100%
I 'top'ped and found system-network-config was still running even though I'd killed the terminal

later
running iptraf as root
later one of my dual cores went to 100%
I 'top'ped and found iptraf was still running even though I'd killed the terminal


 

Version-Release number of selected component (if applicable):
[user@localhost ~]$ uname -r
2.6.31.9-174.fc12.i686
[user@localhost ~]$ rpm -qa gnome-terminal
gnome-terminal-2.28.2-1.fc12.i686


How reproducible:
Not always

Steps to Reproduce:
start a terminal
go to su
1.start an app that has a cell based UI 
2.use it
3.stop it
kill the terminal
 wait
 (it doesn't always happen)

Comment 1 pleabargain 2010-01-14 17:37:04 UTC
Another instance of gnome terminal after death still having a process running:
http://sites.google.com/site/anotherfedora12site/fedora-12-animated-gifs/iptraf100percentofcpuafterkillingterminal.gif?attredirects=0

Comment 2 pleabargain 2010-04-13 14:18:10 UTC
Not happened in awhile marking as works for me.


Note You need to log in before you can comment on or make changes to this bug.