I would suspect a memory leak. Your system will use up all its memory for a while, then use up the virtual memory (swap space) which slows things down by using the hard drive. Eventually it will use up all memory and virtual memory, causing a lockup eventually.
ps aux | grep pd can give you some good info on memory usage. Profilers like valgrind might help you to identify memory leaks too, I think. Chuck On Nov 14, 2007 4:17 PM, B. Bogart <[EMAIL PROTECTED]> wrote: > Hey all, > > Anyhow have an abstraction laying around that gives the current CPU > load? I'm trying to track down a freeze in my long term installation, > and so far I have no indication of why it froze. Perhaps an ever > increasing CPU load could give me a suspect... > > Thanks, > B. Bogart > > _______________________________________________ > PD-list@iem.at mailing list > UNSUBSCRIBE and account-management -> > http://lists.puredata.info/listinfo/pd-list > _______________________________________________ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
