Subject: From: Date:

Re: [ECS] FW: [ECS] Bug in ECSW - System resources eaten up Richard Yee Tue, 25 Aug 1998 11:54:59 -0700

---

The ecs-list rejects messages too large (these messages can take a long
time to retrieve for some people)...


I asked Troy to forward the CFG to me, but seeing that the problem is
most likely fixed thanks to Troy and Mark's efforts, I don't think I
need to post it now.  Compressing the file definetly helps, uncompressed
it was 67k, compressed as 8k.  If anyone wants to see it anyway, just
let me know.

Richard

Ingo wrote:
> 
> Troy,
> 
> What was the message the mail server sent you about rejecting ECS.CFG?
> Was it too large? In that case, WINZIP might help. Or if it isn't too
> large but some other problem, maybe you can simply cut and paste it as
> text into a mail?
> 
> Or you can try the standard method for figuring out what's wrong: make a
> copy of ECS.CFG. Remove all events that are obviously unrelated (for
> instance, maybe you already know that all infrared-related events are
> never triggered). Verify that the resource problem still occurs. Remove
> events one by one, testing each time if the resource problem is still
> there (of course, you will want to make sure that you don't break chains
> of events). If it has gone away, you know that the event you just
> removed, or some other event triggered by it, was responsible. Follow
> the chain of events that get triggered until you figured out which event
> really caused the resource leak. From there, you may even be able to
> narrow it down to one particular line, using the same technique.
> 
> Then just send that particular event from your original saved ECS.CFG,
> rather than your whole ECS.CFG.
> 
> Ingo
>

---