# Unplugging kills my designer

**URL:** <https://forum.inductiveautomation.com/t/unplugging-kills-my-designer/106421>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [May 19, 2025, 4:47pm UTC](https://forum.inductiveautomation.com/t/unplugging-kills-my-designer/106421 "2025-05-19T16:47:29Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [May 19, 2025, 4:56pm UTC](https://forum.inductiveautomation.com/t/unplugging-kills-my-designer/106421/2 "2025-05-19T16:56:34Z")

</div>

You could duplicate the procedure mentioned [here](https://forum.inductiveautomation.com/t/designer-launcher-hangs-when-adding-a-client-script-module-to-the-scriptmanager/104926/6):

> Designer logs are a little trickier; look in `~/.ignition/clientlauncher-data/designerlauncher.log`. There will be a line starting with "Starting Java with the following parameters:". Copy the long command the comes after that, paste it into a new terminal, run it to launch a new Designer. All the logs will be dumped into the terminal as the Designer runs.

Then perform the action that kills the designer; if there's some exception being thrown it should be captured and logged in your running terminal.

---

_[View the full topic](https://forum.inductiveautomation.com/t/unplugging-kills-my-designer/106421)._