RE: [Interfacewm-discuss] horrible memory leak

[Mondragon, I. <ian...@ba...>]

well, i can't say for sure exactly *what* the root of the problem was,
because i killed it with extreme prejudice due to the fact that it bumped my
system's cpu usage up by about 5-10% every couple of seconds.  that means
that within a matter of minutes my machine would be completely useless.  and
yours too.

now it's back to using ~9000K and not growing :-)

i've got one more question...why did you create an ifdefed section of new
methods in IWMWindowManager+Event.m rather than just modifying the existing
methods to accept a plain XEvent?  or am i missing what you were going for?
(although i did notice that the new event handling methods cover more turf
in terms of specific events that are handled...woohoo!)

- ian

ps - check out the current CVS code, install the Default.iwmtheme from the
misc/ directory, run.  i think you'll like what you see.  very NeXT-ish!

-----Original Message-----
From: Chris B. Vetter [mailto:ch...@we...]
Sent: Thursday, September 18, 2003 11:22 AM
To: int...@li...
Subject: Re: [Interfacewm-discuss] horrible memory leak


On Thu, 18 Sep 2003 09:27:09 -0500
"Mondragon, Ian" <ian...@ba...> wrote:
> i found and killed the bug last night.  it was in the method you
> embedded in IWMWindowManager's -run method

Huh? All it does is call -handleEvents: to determine whether an event
should be processed (or not) and if so, calls -handleEvent: to do so.

> (-waitForGodot...whatever that means?!).

Uhm yea, it's a reference to Samuel Beckett's play "Waiting for Godot".
It's about two tramps waiting for a guy called "Godot" -- who never
shows up...

-- 
Chris


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Interfacewm-discuss mailing list
Int...@li...
https://lists.sourceforge.net/lists/listinfo/interfacewm-discuss