Has the update to Premiere CC 2014.2 solved the Memory Leak? I am unable to test, because I finished the project (with a great deal of of trouble and literally hundreds of necessary reboots, i.e. the issues I mention above) using version 2014.1, and subsequently cancelled my Adobe account. So I can't update and run Premiere again to see if there's an improvement with 2014.2.
Has anyone theorized that Premiere and/or OS installations on SSD's might be a problem? Is there anything to this theory? I have my CFA, PEK, and other render/scratch disk files saving in a directory alongside the footage - which is on a separate 3 TB Sata 3.0 drive. The point being to save reads/writes and data accumulation on the SSD wherever possible. However the PROJECT files are being saved on the SSD, in Adobe's default location (the 8.0 file). Please note I don't have any further evidence to support this theory beyond my own computer and experience, which again, is the OS (Win 7 Pro 64-bit) and Adobe Premiere 2014.1 installed on the brand new SSD.
I suppose the follow-up question to ask is, do any of the Adobe QA machines have SSD OS installs similar to this? Or do they do all their QA testing with the default render/scratch disk settings? (Which are completely wrong for smart SSD usage.) Because it is frankly mysterious, and bordering on implausible, that Adobe "can't reproduce this issue." Really now.
Also: I will confirm that the problem has NOTHING to do with switching Premiere project versions mid-stream. In my case, the project was originated and completed exclusively using 2014.1 with the above configuration. So we can go ahead and cross that off as a culprit right now.