Premiere Pro CC 2014 - Bug Report

Question

Just thought I'd report on a ton of bugs that hit me after using CC 2014 on a project though I have no idea what is causing any of them except most likely the underlying Mercury and/or Lumetri Deep Color Engines.
The BIGGEST ISSUE was FLICKERING, most of the other bugs happened in trying to find a way around it. Seemed to experience these problems on two different computers.
Computer 1: Windows 7, Geforce 670 (from memory)
Computer 2: Windows 8, Geforce 750M
Workflow: 3 minute HD music video edited in PP mainly using multicam, direct link grade in Speed Grade utilising the new master clip and clip grade, effects (Red Giant's Universal's diffuse glow, glimmer and Knoll Light Factory, plus RGB curves) and overlays then applied in Premiere with a couple of shots sent to AE for object removal.
Bugs:
Applying perhaps a range of effects seem to results in the image flickering (tried rendering it in software, CUDA and OpenCL engines) and oddly enough only in the second half even though the clips where at same location, same take, same effects and lighting. Often removing the Universal diffuse glow or glimmer effect seem to remove the flicker though the odd clip that didn't have it applied would also randomly flicker so seems like the render engine is freaking out.
At one stage the export resulted in white flashes and even effects not being applied and randomly appearing on/off.
Another time on export the effects were applied but the footage disappeared entirely
Anti-flicker under the motions tab would not remember/display it's value upon loading, displaying 0.00
Anti-flicker on export if perhaps adjusted again after loading the project produced pure RED image on export
Sending a clip to After Effect from Premiere often would not render in Premiere (would produce error, blank or crash) so I had to render proxies in After Effects for it to come across into Premiere. Never had to do this in the previous version of CC.
Overlaying footage and using Screen resulted in a darker image on one clip, maybe something to do with Lumetri applied to a master or independent clip and the order in which effects are being calculated.
Premiere crashed often, usually if it was struggling to display image and then you tried to follow up with commands, move the timeline position or save for instance
Premiere if it didn't crash occasionally it would have laggy play back, and this was just trying to play a single DNxHD clip with no effects applied in a native timeline.
If you need any more information to help fix these bugs let me know and I'll attempt to deliver.

Answer 1

Adobe, I can't believe you're so out of touch on this issue that you are telling people to try removing curves effect. At this point I'm beginning to think that you are deliberately misleading people to downplay this issue. We have told you multiple times that we are a studio with 5 editing stations, all different configurations and graphics cards, and have experienced the issue on several projects and varying levels. This is a MAJOR bug that is crippling business everywhere, that you can read about on several forums, and you are still tell people to 'try removing curves'. For simple edits that don't use many effects, no problems (which is why there are not more complaints because must people do simple edits). As soon as you pile on colorgrading and effects the flickering starts. 
For the rest of you folks trying to get through this, don't waste your time like we did trying to self diagnose the problem removing/changing effects and trying different combos. It will go away one minute, only to randomly return the next. The ONLY true solution we have found is to go back to CC pre 2014. For those of you in mid-project, that means rendering out your work now, maybe without effects if you have to, and start over.
Don't waste your time trying 'removing curves' like Adobe has suggested.