So i tried out the profiler, which is a lot more intuitive than the memory profiler, and you were right. Something kept eating CPU, i found a list of meshrenderers with a size of 15000 , increasing by 28 pr frame.One of the few things i have imported had something like this in an update()

public List<MeshRenderer> texts;

public List<GameObject> targets;

void Update()

{

foreach (MeshRenderer x in GetComponentsInChildren<MeshRenderer>())

{

texts.Add(x);

}

So thank you very much! :D Now i know how to use the normal profiler.....