No, the memory-hungry process I was running was reasonably simple C that I'd written myself. It was semi-contrived, reflecting the extreme of an internal use ca

No, the memory-hungry process I was running was reasonably simple C that I'd written myself. It was semi-contrived, reflecting the extreme of an internal use case, but fundamentally I was just moving around/massaging bytes in big, boringly-malloc'd blocks of memory. I can't swear that there were no Java processes running on the machine at the time, though. And I often have a Windows or Linux VM running in the background.