Yeah, but memory use can be a complex thing in newer operating systems: yes you have memory that the program allocates for variables and code, but you also have memory that the system allocates for library code. Virtual memory will often procrastinate about allocating memory until it is needed, which sometimes means that it is never allocated at all. And, in this case, it isn't showing the memory allocation of the ClarisWorks process, but a parent process.