It seems that FvwmEvent has communication problems that result in freeze of 30 seconds in PositiveWrite.
I get such freeze at random times for all my FvwmEvent instances since 2.3.x versions. It seems recently there are more freezes, probably because enter_window and leave_window events are added. It is hard to reproduce on purpose. One guy said he can reproduce this on almost every FvwmEvent start or restart, but I can't do this with his config. I sometimes see this when some kind of grabbing is done (new window added while with the busy cursor) or on a moderate system load, but this is not deterministic. The error is this: [FVWM][PositiveWrite]: <<ERROR>> Failed to read descriptor from 'FvwmEvent FvwmEvent-Alias': - data available=N - terminate signal=N The strange thing is that the offender (FvwmEvent) is not killed as would be guessed from the source code, but remains to be functional after the freeze until the next freeze. What is the best way to debug this? Chris, are you here? Regards, Mikhael. -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
