Yeah... that wouldn't be an nUI error directly as nUI cannot directly access or manipulate memory... which is not to say that nUI may not have agitated the situation. Seeing that it happened while fetching aura data does not surprise me. I suspect that is directly related to the aura FPS leak problem in nUI5.