On Wed, 18 Nov 1998, christ wrote:
> technically speaking, x-apps are generally not children of your WM unless
> they're started by the WM (ie from a pulldown menu or maybe from the
> afterstep "dock" or whatever). stuff started from the command line/xinitrc
> will be children of either the command-session that started them or maybe
> of xinit.
This happens to applications invoked both ways. Gnome gmc/panel
are invoked from .xsession, but gqview/gqmpeg are invoked from windowmaker
menus -- and those 4 are the prime offenders. OTOH,a quick check shows
that program invoked from rxvt's do not exhibit this behavior.
> however, this is beside the point...as netscape has proven time and again,
> it is possible to ignore every signal in the book (save SIGKILL) and keep
> running regardless of the right thing to do.
Yeah, I suppose its not necessarily fair to include netscape in
this problem, as netscape wins awards for finding the most creative ways
of dying. Sometimes as an idle process, sometimes maxing the COU.
> however, the gnome team being very public in their development cycle, would
> probably be glad to hear about this bug...and they might even have a solution
> for ya =)
Except that it isn't all gnome applications. gqview/gqmpeg are
straight GTK/imlib... which then raises the question that maybe there's a
massive fault in GTK or imlib. (Let me remind you that its not just that
the applications are left running -- they shoot up to collectively
near-100% cpu usage.)
-Alex
__________________ T
\ Alex Winbow \______________ Houston/Austin E
\ [EMAIL PROTECTED] \_________________ U.of X
\________ http://uts.cc.utexas.edu/~awinbow \ A
\_____________________________________\ S
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]
