I wrote the patch; the latest version is attached.
Other modules have the same problem; however, since they aren't used as much
the problem is not as visible.
According to Michael Tiefenback:
> On Fri, 30 Jan 1998, Jeff Wiegley wrote:
>
> > [snip]
> > Well today Things were horrible and so I did top to see if accidentally
> > had some program I wrote churning out zombies or other detached processes
> > from my thesis program. And what I found was I had seven instances of
> > FvwmButtons running and they were all fighting for 100%CPU attention.
> >
> > I read the mailing list archives and noticed that others are having
> > similar problems but I couldn't find a fix for it.
>
> My feeble memory tells me that I once suffered from this, too, in long-ago
> days (perhaps pre-version2), and that it was a (sometime later) fixed
> problem with FvwmButtons not noticing that its pipes to its parent were
> dead and gone. The fix at the time was a few lines dealing with testing
> the read pipe returns, exiting on closure of the pipes. I haven't noticed
> it on my own office 2.0.46 setup, nor at home on the (2.0.43?) setup I'm
> running. I hope this helps someone, although I don't see how this
> particular error could have crept back into the code.
>
> Michael Tiefenback
>
> --
> Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
> To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
> message to majordomo_at_hpc.uh.edu.
> To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
--
Grant McDorman <grant_at_isgtec.com>
ISG Technologies, Inc. http://www.isgtec.com
Mississauga, Ontario, Canada
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
- application/pgp-signature attachment: stored
Received on Fri Jan 30 1998 - 15:34:14 GMT