# 8.0.3 RC1 Memory problem (clock drift) with Tree Component and Embedded View

**URL:** <https://forum.inductiveautomation.com/t/8-0-3-rc1-memory-problem-clock-drift-with-tree-component-and-embedded-view/26867>\
**Category:** Ignition Early Access\
**Created:** [July 25, 2019, 8:15am UTC](https://forum.inductiveautomation.com/t/8-0-3-rc1-memory-problem-clock-drift-with-tree-component-and-embedded-view/26867 "2019-07-25T08:15:47Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![roberto.camp](https://avatars.discourse-cdn.com/v4/letter/r/a5b964/32.png) [@roberto.camp](https://forum.inductiveautomation.com/u/roberto.camp)\
**Post date:** [July 25, 2019, 9:53am UTC](https://forum.inductiveautomation.com/t/8-0-3-rc1-memory-problem-clock-drift-with-tree-component-and-embedded-view/26867/2 "2019-07-25T09:53:36Z")

</div>

Ok, small follow-up.

I’ve managed to fix this problem using the info in this thread: [[Question] Null values causing errors in Perspective](http://forum.inductiveautomation.com/t/question-null-values-causing-errors-in-perspective/23390/3)

I just added a validation Script (it can check for “None”), Expressions worked, but it still gave off a warning, albeit not crashing the gateway.

The problem was caused by the lack of selection in the Tree. Since the “selection” and “selectionData” properties on the Tree are dynamic (and therefore empty if nothing is selected) it caused problems on the binding.

These problems/warnings on the binding are to be expected, but they shouldn’t crash the gateway, so, maybe a bug?

---

_[View the full topic](https://forum.inductiveautomation.com/t/8-0-3-rc1-memory-problem-clock-drift-with-tree-component-and-embedded-view/26867)._