On Sat, 29 Oct 2005 16:51:15 -0500 Paul S. [EMAIL PROTECTED]
babbled:
When I let e run for a while, it takes a literal second for the icons on
the ibar or engage to respond or be highlighted and zoom out when I put
my mouse over it. This is after letting e run for a few hours. I
noticed on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 30 Oct 2005, Carsten Haitzler wrote:
On Sat, 29 Oct 2005 17:38:13 -0500 Paul S. [EMAIL PROTECTED]
babbled:
Found it. I disabled both the dropshadow and monitor modules.
Paul
unlikely that it's dropshadow. maybe monitor - but not
I can confirm that E has gotten a lot laggy lately.
Besides the one-second redraw on the borders that I noticed some time
ago, when the app is uniconified, now when I move windows around, I can
see the exposure events more clearly than ever before. Using the ibar
takes ~90% of the cpu, unlike the
Il y a peu, Carsten Haitzler [EMAIL PROTECTED] nous a dit :
On Sun, 30 Oct 2005 12:34:13 +0200 $B'#'Z'\'d'`'b(B
$B','`'X'e'g'Q'b'`'S(B [EMAIL PROTECTED]
babbled:
I can confirm that E has gotten a lot laggy lately.
Besides the one-second redraw on the borders that I noticed some time
ilLogict wrote:
For instance, open an internal config app (window locks, remember, focus
settings, eap editor) and toggle between basic/advanced settings. You will see
that it takes a long time (about 1s here) before the window border
reappears...
instant action on my system
--
Morten
On Sun, 30 Oct 2005 12:41:43 +0100
ilLogict [EMAIL PROTECTED] wrote:
Hello!
For instance, open an internal config app (window locks, remember,
focus settings, eap editor) and toggle between basic/advanced
settings. You will see that it takes a long time (about 1s here)
before the window
It seems to be a creeper, getting laggier very slowly over the
session. Adding and removing stuff may just trigger the problem to
start from no lag. It might still creep up to laggy.
Makes it very hard to debug.
pgpfOabG9YZqW.pgp
Description: PGP signature
On Sun, 30 Oct 2005 13:20:28 +0100
ilLogict [EMAIL PROTECTED] wrote:
Hello!
Strange, as I don't have engage, after testing, it seems it is due to
the pager
(???)
After unloading it, everything reponds as before (starting apps,
closing apps).
Cheers!
You're right, it seems both pager
On Sun, 30 Oct 2005 22:28:39 +1000
David Seikel [EMAIL PROTECTED] wrote:
It seems to be a creeper, getting laggier very slowly over the
session. Adding and removing stuff may just trigger the problem to
start from no lag. It might still creep up to laggy.
Makes it very hard to debug.
I
On Sun, 30 Oct 2005 13:20:28 +0100
ilLogict [EMAIL PROTECTED] wrote:
Hello!
Strange, as I don't have engage, after testing, it seems it is due to
the pager
(???)
After unloading it, everything reponds as before (starting apps,
closing apps).
Cheers!
Doing some more testing, it seems
On Sun, 30 Oct 2005 06:37:06 -0600
Jesse Luehrs [EMAIL PROTECTED] wrote:
...except for how the issue stopped being caused by engage just now.
But it's still consistent with ibox and pager.
Jesse
Scratch that. Engage causes the issue only with the weird resizing
thing that the focus settings
Sent this out earlier, but it got blocked for being too big... you can
grab the attachment at http://doy.illinexus.org/gprof_tests.tar.bz2
On Sun, 30 Oct 2005 06:31:36 -0600
Jesse Luehrs [EMAIL PROTECTED] wrote:
I think this is a different issue... our (me and illogict) issue is
always
On Mon, 31 Oct 2005 00:21:25 -0600 Jesse Luehrs [EMAIL PROTECTED] babbled:
Sent this out earlier, but it got blocked for being too big... you can
grab the attachment at http://doy.illinexus.org/gprof_tests.tar.bz2
On Sun, 30 Oct 2005 06:31:36 -0600
Jesse Luehrs [EMAIL PROTECTED] wrote:
When I let e run for a while, it takes a literal second for the icons on
the ibar or engage to respond or be highlighted and zoom out when I put
my mouse over it. This is after letting e run for a few hours. I
noticed on top that E is using 65mb of memory. This is weird.
Something seems amiss.
Also, I've done some further investigation, it's using 13% CPU too.
I've never had this problem with e17 before. I have a p4 @ 3 GHz and
512MB of RAM, so it's a beefy enough machine to handle it. My theory is
a coding error of some sort behind e, not the modules itself. I can't
pinpoint it, I
Found it. I disabled both the dropshadow and monitor modules.
Paul
On Sat, 2005-10-29 at 17:00 -0500, Paul S. wrote:
Also, I've done some further investigation, it's using 13% CPU too.
I've never had this problem with e17 before. I have a p4 @ 3 GHz and
512MB of RAM, so it's a beefy enough
On Sat, 29 Oct 2005 17:38:13 -0500 Paul S. [EMAIL PROTECTED]
babbled:
Found it. I disabled both the dropshadow and monitor modules.
Paul
unlikely that it's dropshadow. maybe monitor - but not dropshadow. all the
defaults here and e doesnt leak etc. etc. etc.
On Sat, 2005-10-29 at 17:00
17 matches
Mail list logo