Comments on: Konfabulator. http://blog.founddrama.net/2004/05/konfabulator/ getOblique(); Thu, 08 Jan 2009 21:06:38 +0000 http://wordpress.org/?v=2.7 hourly 1 By: found_drama » Blog Archive » Konfabulicious. http://blog.founddrama.net/2004/05/konfabulator/comment-page-1/#comment-224 found_drama » Blog Archive » Konfabulicious. Wed, 16 Nov 2005 18:10:01 +0000 http://blog.founddrama.net/?p=306#comment-224 [...] To follow up on my Konfabulator post from late May… And while I’m a little late on this: Daring Fireball’s ‘Dashboard vs. Konfabulator’. [...] [...] To follow up on my Konfabulator post from late May… And while I’m a little late on this: Daring Fireball’s ‘Dashboard vs. Konfabulator’. [...]

]]> By: Anonymous http://blog.founddrama.net/2004/05/konfabulator/comment-page-1/#comment-6 Anonymous Tue, 30 Nov 1999 00:00:00 +0000 http://blog.founddrama.net/?p=306#comment-6 I never liked Konfabulator. Granted it was a pretty tool, but the programming was horrendous. It crashed frequently, ate memory, and had a ton of memory leaks. I was able to run 15 apps concurrently, including SETI@Home and Folding@Home clients and still never experienced a slow down like I did with Konfabulator. Apparently, the design of KFB was such that its leaks would quickly fill up memory and its constant memory accesses would then be forced to be swapped out and in time and time again. Major drag on the system. I agree with your assesement.<br /><br />Quick point that you may already know:<br />At the terminal prompt type 'top' to see the current running processes as well as memory usage.<br /><br />At the terminal type 'leaks [appname]' to see the memory leaks for a given program. KFB, at the version that I used it on my old computer had quite a hefty list.<br /><br />-m I never liked Konfabulator. Granted it was a pretty tool, but the programming was horrendous. It crashed frequently, ate memory, and had a ton of memory leaks. I was able to run 15 apps concurrently, including SETI@Home and Folding@Home clients and still never experienced a slow down like I did with Konfabulator. Apparently, the design of KFB was such that its leaks would quickly fill up memory and its constant memory accesses would then be forced to be swapped out and in time and time again. Major drag on the system. I agree with your assesement.

Quick point that you may already know:
At the terminal prompt type ‘top’ to see the current running processes as well as memory usage.

At the terminal type ‘leaks [appname]‘ to see the memory leaks for a given program. KFB, at the version that I used it on my old computer had quite a hefty list.

-m

]]>