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 (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: 0Problem 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.hdmpThese files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_java.exe_a2d6d8c77f793eab67b56e8c7e988802a114153_54634130_cab_42e4627b-a30e-49c1-9e48-741ac7a52879Analysis 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
But they even followed up with me to make sure the problem didn't come back.