# Corrupted Ignition Screen

**URL:** <https://forum.inductiveautomation.com/t/corrupted-ignition-screen/80606>\
**Category:** Ignition\
**Tags:** ignition81, vision\
**Created:** [October 17, 2023, 5:22pm UTC](https://forum.inductiveautomation.com/t/corrupted-ignition-screen/80606 "2023-10-17T17:22:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Muhammad\_Saim](https://avatars.discourse-cdn.com/v4/letter/m/7ab992/32.png) [@Muhammad\_Saim](https://forum.inductiveautomation.com/u/Muhammad_Saim)\
**Post date:** [October 17, 2023, 5:22pm UTC](https://forum.inductiveautomation.com/t/corrupted-ignition-screen/80606/1 "2023-10-17T17:22:30Z")

</div>

Hello

We seem to have an issue with one of our vision window where if you edit anything within the window (component, dataset, script...etc) it seems to corrupt it and the window won't open anymore. I can initially open the vision window when I import, but then if I edit anything, the loading thing at the top right just spins and it says very high power usage in task manager. I've attached the screen along with the templates. I want to know two things how can I fix this, and how can I prevent this in the future.  
[WorkingScreenWhole.zip](https://forum.inductiveautomation.com/uploads/short-url/5OtyTr9ASICHoYUtlfUNXilGrCL.zip) (68.6 KB)

Thank you  
From Muhammad Saim

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [October 17, 2023, 7:19pm UTC](https://forum.inductiveautomation.com/t/corrupted-ignition-screen/80606/3 "2023-10-17T19:19:33Z")

</div>

- Sounds like a circular binding or propertyChange event. (One binding or event sets a value to one property, which is used in another binding or event, that then modifies the original property again. Possibly in a more complex circle.)

- Don't do that. Make sure one property changes and/or bindings only "flow" in one direction. Use custom properties to hold intermediate values if necessary.

- Audit your propertyChange event scripts and make sure all code with them is conditioned with a check for the intended `event.propertyName`. **All** changes to **any** properties of a given component run through the **one** script.