Is Constructor loading all textures into memory?

I've been moving my texture directories into Constructor, (not the most intuitive process btw), and the first time through after manually creating each directory (I have about sixty in that folder) and adding in about seventy five percent of the files Constructor just "went away".

I tried to restart it and it seem to hang forever then again just "disappeared". The question I have is perhaps it because it it struggling to index my textures, i.e. the quantity that I'm trying to get it to load? I have over a GB of them. (Yeah, yeah...I know...it's a fetish thing...).

I have started again and I'm being a little more, how would you say it, selective? in the directories that I'm loading, but I'd hate down the line to have this happen and run into the same issue with it not loading like this and have to start this process over again. Currently it does load but it takes nearly five minutes and appears to be loading all the textures into memory.

Is this to be expected? 3DWS had a problem with this in one of the older builds but it was, as far as I can tell corrected.

Here is shot of the memory use in taskmanager:


EDIT: OK, after sitting idle for about fifteen minutes it dropped back down to around 10mb, but if you select another texture, it jumps back up to the 783mb in the task manager and becomes "sluggish" again.