# Designer launcher hangs when adding a client script module to the ScriptManager **URL:** \ **Category:** Ignition 8.3 Early Access\ **Created:** [April 9, 2025, 11:18pm UTC](https://forum.inductiveautomation.com/t/designer-launcher-hangs-when-adding-a-client-script-module-to-the-scriptmanager/104926 "2025-04-09T23:18:30Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [April 10, 2025, 10:42pm UTC](https://forum.inductiveautomation.com/t/designer-launcher-hangs-when-adding-a-client-script-module-to-the-scriptmanager/104926/6 "2025-04-10T22:42:09Z")
You can get a thread dump from the Designer using the `jstack` util. Run `jps`, find the process ID for your Designer, then use `jstack` to dump the threads. Post both a Gateway and Designer thread dump here, taken while hanging. 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. --- _[View the full topic](https://forum.inductiveautomation.com/t/designer-launcher-hangs-when-adding-a-client-script-module-to-the-scriptmanager/104926)._