Overview
Renderer crashes in OpenFin applications can be caused by various factors, including out-of-memory issues, hardware acceleration problems, and interference from security software. This guide is designed to help you identify and resolve these issues when troubleshooting renderer crashes.
Error Dialog:
Troubleshooting Steps:
Depending on the level of access you have as end user, we would recommend contacting your system admin or application support team when reviewing some of the troubleshooting steps below.
- Review security software logs, check windows event viewer records. This is to determine if security software is terminating or disrupting any of the OpenFin processes.
Guide: Learn how to navigate the Windows Event Viewer with the guide on "How to use Windows Event Viewer." - Renderer crashes can sometimes be related to GPU or hardware acceleration issues. You can try disabling hardware acceleration to see if it resolves the problem.
Guide: A guide on how to disable the GPU can be found here: "Disabling the GPU" - Running OpenFin in a Virtualised environment requires some setup that involves certain runtime flags that need to be applied on the machine. Check that these have been applied.
Guide: If you are running OpenFin on a virtualised environment, ensure you review our guide on "OpenFin running in a Virtual Desktop Environment" - Examine the memory consumption of the application that is triggering the renderer crash. Elevated memory utilization on the host system may be a contributing factor to the renderer crash.
Guide: You can profile the use of the memory of your application by using the google tools described here: https://developer.chrome.com/docs/devtools/memory-problems/allocation-profiler/. -
If the issue persists even after applying runtime arguments, consider enabling Diagnostics Mode to collect detailed logs and crash reports.
Guide: Follow our guide on "Enabling Diagnostics Mode/Crash Reporting" for step-by-step instructions. Share the collected data with OpenFin support for further analysis.
Comments
0 comments
Please sign in to leave a comment.