# Designer repeatedly crashing **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [February 23, 2023, 11:10pm UTC](https://forum.inductiveautomation.com/t/designer-repeatedly-crashing/70255 "2023-02-23T23:10:54Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![ken.maze](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ken.maze/32/85876_2.png) [@ken.maze](https://forum.inductiveautomation.com/u/ken.maze)\ **Post date:** [February 23, 2023, 11:10pm UTC](https://forum.inductiveautomation.com/t/designer-repeatedly-crashing/70255/1 "2023-02-23T23:10:54Z")
Hi, I have been having repeated crashes of designer this afternoon. I tried restarting my machine, restarting the Ignition server, then even upgraded Ignition to 8.1.25 (this is on a test server), and still it will hang up somewhat randomly. It seems to hang up when I try to open a perspective binding. I have even noticed that opening a binding will be somewhat slow, then it gets to a point where it freezes. I have minimized the operations happening on the components I am working on, and it still crashes. I did notice later that I am having Java crashes, see below for Windows Event Logger, thread dump, and wrapper log excerpt Thanks for any help.. Ken Thread Dump: [JDC KAI Test -USCHIZWKAI3001\_thread\_dump20230223-180257.json](https://forum.inductiveautomation.com/uploads/short-url/oqgmixel1ho3UcJI2FMwVlY4X7G.json) (142.4 KB) Event Logger output: > Faulting application name: java.exe, version: 11.0.17.0, time stamp: 0x6342723a > Faulting module name: jvm.dll, version: 11.0.17.0, time stamp: 0x6342721d > Exception code: 0xc0000005 > Fault offset: 0x0000000000107cb0 > Faulting process id: 0xadc > Faulting application start time: 0x01d947d4a7c4532c > Faulting application path: C:\Users\kmaze.ignition\cache\resources\runtimes\11.0.17\bin\java.exe > Faulting module path: C:\Users\kmaze.ignition\cache\resources\runtimes\11.0.17\bin\server\jvm.dll > Report Id: 4af06a1b-79bd-4c55-b1b0-46ee10f567f7 > Faulting package full name: > Faulting package-relative application ID: Event Logger output for crash report > Fault bucket , type 0 > Event Name: APPCRASH > Response: Not available > Cab Id: 0 > > Problem signature: > P1: java.exe > P2: 11.0.17.0 > P3: 6342723a > P4: jvm.dll > P5: 11.0.17.0 > P6: 6342721d > P7: c0000005 > P8: 0000000000107cb0 > P9: > P10: > > Attached files: > \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER95F3.tmp.dmp > \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER98B3.tmp.WERInternalMetadata.xml > \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9902.tmp.xml > \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9910.tmp.csv > \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER996F.tmp.txt > \?\C:\Users\kmaze\AppData\Local\Temp\WER9AAA.tmp.appcompat.txt > \?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash\_java.exe\_a2d6d8c77f793eab67b56e8c7e988802a114153\_54634130\_cab\_42e4627b-a30e-49c1-9e48-741ac7a52879\memory.hdmp > > These files may be available here: > \?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash\_java.exe\_a2d6d8c77f793eab67b56e8c7e988802a114153\_54634130\_cab\_42e4627b-a30e-49c1-9e48-741ac7a52879 > > Analysis symbol: > Rechecking for solution: 0 > Report Id: 4af06a1b-79bd-4c55-b1b0-46ee10f567f7 > Report Status: 4 > Hashed bucket: > Cab Guid: 0 And here is the wrapper log around the time of the crash: > INFO | jvm 1 | 2023/02/23 17:53:25 | I [p.DesignSession] [22:53:25]: WebSocket disconnected from session. session-project=CEVAKitRandoScan > INFO | jvm 1 | 2023/02/23 17:53:25 | W [P.WebSocketChannel] [22:53:25]: Websocket connection errored out. Keeping session open. > INFO | jvm 1 | 2023/02/23 17:53:25 | java.nio.channels.ClosedChannelException: null > INFO | jvm 1 | 2023/02/23 17:53:25 | at org.eclipse.jetty.websocket.core.internal.WebSocketSessionState.onEof(WebSocketSessionState.java:169) > INFO | jvm 1 | 2023/02/23 17:53:25 | at org.eclipse.jetty.websocket.core.internal.WebSocketCoreSession.onEof(WebSocketCoreSession.java:253) > INFO | jvm 1 | 2023/02/23 17:53:25 | at org.eclipse.jetty.websocket.core.internal.WebSocketConnection.fillAndParse(WebSocketConnection.java:482) > INFO | jvm 1 | 2023/02/23 17:53:25 | at org.eclipse.jetty.websocket.core.internal.WebSocketConnection.onFillable(WebSocketConnection.java:340) > INFO | jvm 1 | 2023/02/23 17:53:25 | at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:314) > INFO | jvm 1 | 2023/02/23 17:53:25 | at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:100) > INFO | jvm 1 | 2023/02/23 17:53:25 | at org.eclipse.jetty.io.SelectableChannelEndPoint$1.run(SelectableChannelEndPoint.java:53) > INFO | jvm 1 | 2023/02/23 17:53:25 | at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.runTask(AdaptiveExecutionStrategy.java:416) > INFO | jvm 1 | 2023/02/23 17:53:25 | at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.consumeTask(AdaptiveExecutionStrategy.java:385) > INFO | jvm 1 | 2023/02/23 17:53:25 | at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.tryProduce(AdaptiveExecutionStrategy.java:272) > INFO | jvm 1 | 2023/02/23 17:53:25 | at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.lambda$new$0(AdaptiveExecutionStrategy.java:140) > INFO | jvm 1 | 2023/02/23 17:53:25 | at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:411) > INFO | jvm 1 | 2023/02/23 17:53:25 | at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:934) > INFO | jvm 1 | 2023/02/23 17:53:25 | at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1078) > INFO | jvm 1 | 2023/02/23 17:53:25 | at java.base/java.lang.Thread.run(Unknown Source) > INFO | jvm 1 | 2023/02/23 17:53:25 | W [P.WebSocketChannel] [22:53:25]: Websocket connection closed unexpectedly. code=1006, reason=Session Closed, codeMeaning=Normal Closure, codeDescription=Reserved. Indicates that a connection was closed abnormally (that is, with no close frame being sent) when a status code is expected. > INFO | jvm 1 | 2023/02/23 17:53:25 | I [p.DesignSession] [22:53:25]: WebSocket disconnected from session. session-project=CEVAKitRandoScan ---
**Author:** ![ken.maze](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ken.maze/32/85876_2.png) [@ken.maze](https://forum.inductiveautomation.com/u/ken.maze)\ **Post date:** [February 24, 2023, 9:04pm UTC](https://forum.inductiveautomation.com/t/designer-repeatedly-crashing/70255/2 "2023-02-24T21:04:53Z")
Sometimes I instead get application hangs. The application is unresponsive, and I have to use Task Manager to kill off Zulu > The program java.exe version 11.0.17.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel. > Process ID: 4780 > Start Time: 01d948501745bc20 > Termination Time: 4294967295 > Application Path: C:\Users\kmaze.ignition\cache\resources\runtimes\11.0.17\bin\java.exe > Report Id: b5851914-65bd-4cbf-a8b8-5d14ad7ba089 > Faulting package full name: > Faulting package-relative application ID: > Hang type: Top level window is idle ` ---
**Author:** ![Fabio\_Aufinger](https://avatars.discourse-cdn.com/v4/letter/f/35a633/32.png) [@Fabio\_Aufinger](https://forum.inductiveautomation.com/u/Fabio_Aufinger)\ **Post date:** [April 4, 2023, 1:59pm UTC](https://forum.inductiveautomation.com/t/designer-repeatedly-crashing/70255/3 "2023-04-04T13:59:49Z")
Hi, I have similar issues on 8.1.24. Can someone please help? ---
**Author:** ![ken.maze](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ken.maze/32/85876_2.png) [@ken.maze](https://forum.inductiveautomation.com/u/ken.maze)\ **Post date:** [May 1, 2023, 7:53pm UTC](https://forum.inductiveautomation.com/t/designer-repeatedly-crashing/70255/4 "2023-05-01T19:53:34Z")
I would suggest you call support, they were very responsive to me. We didn't figure out what the problem was, it seemed to hae spontaneously resolved itself 🙄 But they even followed up with me to make sure the problem didn't come back.