By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 259 - kompare does not always terminate properly, leaving the process running
Summary: kompare does not always terminate properly, leaving the process running
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: tdesdk (show other bugs)
Version: R14.0.0 [Trinity]
Hardware: All All
: P1 major
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2010-09-07 23:34 CDT by Darrell
Modified: 2013-05-09 11:44 CDT (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name: kompare

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Darrell 2010-09-07 23:34:14 CDT 
Closing kompare does not always terminate the process. The process ID remnant will look like this:

18853 ?        S      0:08 kompare -caption Kompare -icon kompare -miniicon kompare -o

Solution is to ensure kompare terminates properly.
Comment 1 Darrell 2010-09-08 00:50:36 CDT 
More than one process might be left running.
Comment 2 Timothy Pearson 2012-06-12 23:27:56 CDT 
Is this still happening in the R14.0 GIT?
Comment 3 Darrell 2012-06-12 23:34:56 CDT 
A coincidence you ask. :-) I have not paid attention but today while looking through my bug list I saw this bug report. I made a note to watch this for the next several days. If the bug persists I'll add a note. If not then I'll close the report.
Comment 4 Darrell 2012-06-13 01:12:37 CDT 
I did not need to wait long. :-)

I opened two instances of kompare and then closed both. kompare remained in the process list (ps ax):

25816 ?        S      0:01 kompare -caption Kompare -icon kompare -miniicon kompare -o

The bug is related to opening more than one concurrent instance, but based upon some nominal testing, only when the subsequent instances are opened/spawned from within the first instance using File/Compare Files (Ctrl-C).

When opening multiple instances outside of kompare, say all instances from the mini cli or menu, then no instance remains in the process list when all are closed. Each multiple instance appears in the ps process list, but each one disappears when that instance is closed.

When the multiple instances are opened/spawned from within the first instance, the remaining process ID is that of the first instance.

When the multiple instances are opened/spawned from within the first instance, only the first instance appears in the process list.

When opened externally, each instance appears separately in the process list.
Comment 5 Timothy Pearson 2012-06-13 01:19:45 CDT 
OK, thanks for testing.

When you provide information to a NEEDINFO bug, please mark it as NEW so that I know the bug still needs work.

Thanks!
Comment 6 Timothy Pearson 2013-05-09 10:24:47 CDT 
Fixed in GIT hash 39f8de9.

Thanks for reporting!
Comment 7 Darrell 2013-05-09 11:44:55 CDT 
Rebuilt and tested. Opening multiple instances of kompare using File/Compare Files (Ctrl-C) results in only one process at all times. When the last instance is closed no orphan processes remain. Good job and thanks!