On Wed, Aug 14, 2002 at 11:22:13AM +0200, fvwm-workers wrote: > On Wed, Aug 14, 2002 at 01:17:54AM -0600, S. Anderson wrote: > > On Tue, Aug 13, 2002 at 02:43:32PM -0600, S. Anderson wrote: > > > On Tue, Aug 13, 2002 at 11:40:28AM +0200, Dominik Vogt wrote: > > > > On Mon, Aug 12, 2002 at 10:07:14PM -0600, S. Anderson wrote: > > > > > I may have found a bug, to reproduce... > > > > > > > > > > 1. I start fvwm without a rc file, > > > > > 2. then execute gkrellm from a xterm, > > > > > 3. then I click on the gkrellm window(not the fvwm decorations) and > > > > > wiggle it around. > > > > > 4. repeat step 3 a few times. > > > > > > > > > > fvwm, gkrellm and X start fighting for cpu use. Memory used starts > > > > > filling up really fast. And I cant do anything execpt ctrl-alt-bkspce. > > > > > > > > > > GKrellM 1.2.13 > > > > > gtk 1.2.10 > > > > > Xfree86 4.2.0 > > > > > Linux 2.4.19 i686 AuthenticAMD > > > > > [EMAIL PROTECTED] ~ % fvwm-config -i > > > > > Package: fvwm > > > > > Version: 2.5.3 > > > > > > > > With the same versions, it doesn't happen here. Is the fvwm-2.5.3 > > > > latest CVS? > > > > > > > > > > yes updated on aug 12th. I downloaded fvwm-snap-20020810 and It doesnt > > > have this problem. I just figured out, If I > > > #undef EXPERIMENTAL_ANTI_RACE_CONDITION_CODE > > > in fvwm/events.c at line 1081 I dont have this problem anymore. > > > is the experimental anti race condition code important, should I not > > > disable it? > > It's experimental. And it's meant to reduce the chance of such > ConfigurRequest/ConfigureNotify races happening, but it looks like > my latest addition has a bug. > > > > also I forg?t to mention I am using gcc 3.1.1, and It is not only > > > gkrellm, but xmms and xine too. > > > > ok, some more info... > > this is the output that fvwm spits out. I get this race condition > > right before it prints 'cn_count = 22507546', I let fvwm run until > > my system ran out of resources. > > > [EMAIL PROTECTED] ~ % fvwm > ... > > cn_count = 457502 > ... > > cn_count = 22507546 > > Uh, oh! 22.5 million ConfigureNotify events that are going to be > sent to the application? No wonder it hogs CPU. Maybe I'm using > an uninitialised variable.
Fixed. Bye Dominik ^_^ ^_^ -- Dominik Vogt, mail: [EMAIL PROTECTED], phone: 0721/91374-382 Schlund + Partner AG, Erbprinzenstr. 4-12, D-76133 Karlsruhe -- 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]
