Thanks for your helpful comments. Urs-I haven’t yet tried it, but VMMap _looks_ like a very useful additional utility. By the way, I should also have pointed out that Stuart’s CHKMEM only works on 32-bit Windows systems. VMMAP, too, is Windows-centric (it’s from Microsoft), and is, I believe, compatible with 64-bit systems. However, Google turns up some discussions about problems with using it on 64-bit machines.

And Yair, thanks, too, for pointing out that Stuart’s submission uses undocumented functionality. I should have pointed that out myself.

We’ve struggled in the past with whether or not to steer away from featuring submissions that use undocumented commands. Sometimes they’re just too good to pass up! (Some of your own files fall in that category, by the way.)

Cheers,
Brett

However, users should note that Chkmem relies on undocumented features (feature ‘memstats’ and ‘dumpmem’) which are unsupported by MathWorks and might break without prior warning in a future release. I personally have no problem with this, but it should be noted for the record.

users interested in these undocumented memory features may also be interested in checking the output of the related feature(’processmem’), which is not used by Chkmem.

Yair

in addition to this utility, i’d like to alert the wintel system users to a recent piece from windows sysinternal: VMMAP (1.1), available here

http://technet.microsoft.com/en-us/sysinternals/dd535533.aspx

which does an amazing job in giving you all the information you ever wanted (re memory issues)…

best
urs