Working Memory transferred itself to the Pagefile???

I was using Firefox's inPrivate browsing to print (to PDF) a lot of pages of porn video information (you know like the information you read before you download the porn) that kinda stuff. Anyways, I was using a Firefox addon called Universal Print to do that. Usually, it takes a lot of RAM to keep about 100 tabs open (with pictures and all that). The ram size for the firefox session was about 2.5 gigs (I have 10 gigs of RAM, so it's awesome). I noticed in Task Manager that that the same amount of ram that usually shows up in the "Working Set" column was instead in the "Commit Size" column. My understanding is that the Commit Size represents how much pagefile space is being used by each process, so I am wondering why firefox would put that in the Pagefile rather than the RAM. This has never happened before. Could it be that inPrivate likes to use the pagefile rather than the RAM? That would not make sense because RAM is a bajillion times faster and has a better latency than the pagefile.

Any ideas?

 

So I can print them all at once with an add-on