JustTrace supports 32-bit Windows, but is much more constrained in terms of available memory address space. It appears from your exception report that you're using "Attach to process" with the memory profiler, which is based on using a memory debugger. I suggest you try option number 3. from the previous reply in this thread. This will bypass the memory debugger and get you closer to taking a snapshot.
Still, taking a snapshot of a process that has N bytes of managed memory, requires about 2-5x N of additional memory for processing. For example, if your leaking process is taking 1GB of managed memory, then JustTrace will need about 2-5GB of free memory to process the snapshot. Obviously this is nearly impossible on a 32-bit operating system, hence the "out-of-memory" errors you see.
Share what you think about JustTrace & JustMock with us, so we can become even better! You can use the built-in feedback tool inside JustTrace, our forums
, or our JustTrace