Debugging FME Workbench Has Stopped Working Error

Debbi L
Debbi L
  • Updated


You may come across the following error when starting up FME Workbench or FME Data Inspector or running a workspace. This error may occur after installing a new version/build of FME on your machine. If you encounter this error when running a workspace, please refer to this article to narrow down the issue.

The faulting module may mention Qt, which is the library FME graphical user interface (GUI) is based on but this may not be the faulting module. See below for a screenshot of an example dialog on Windows.

If you run into a crash, hang, or error state similar to the one shown above that can be reliably reproduced , please go to the appropriate section for the operating system of your machine, follow the instructions outlined, and send the information as an attachment when creating a support case here.



For crashes on Windows machine, please gather the following three pieces of information.

1. Windows Event Viewer

Launch the Windows Event Viewer. Go to the Start menu (Windows key or select Windows icon on the bottom left of the screen), type “Event Viewer” into the search box, and click the result. This should open the Event Viewer application.

Select Application under Windows Logs on the event viewer dialog on the left and search for Error level events relating to fme.exe, fmeworkbench.exe, or fmedatainspector.exe. You can also narrow the number of events to look through by looking at the date and time of events.

Once you have found the event log relating to the FME crash, please select the General tab and copy the information into a text file and save.

2. Process Monitor

Process Monitor is a utility application which monitors and displays in real-time all file system activity on a Windows operating system. Process Monitor can be downloaded from:  

Extract and open Process Monitor. You'll notice events scrolling by; press CTRL+E to stop the capture, and CTRL+X to clear the screen. Next, press CTRL+L to open the Filter window and if possible click the Reset button. Then add the following four filters:
1. Process Name 2. contains 3. fme then 4. Include

The final result should look like this:

Click OK. Next, open Workbench and open the workspace that is failing. Start Process Monitor capturing (CTRL+E) and start the workspace.
Once the workspace is in the crash, hang, or error state, stop Process Monitor capturing (CTRL+E).
Save the capture to a file of your choice. See screenshot below.

3.System Information Report

Download and run the system_information.bat file from the following Gathering System Information article. Please run the .bat file as administrator. The .bat file will gather basic information about your system and no settings will be changed by the script.

The output is a basic html file named FMEReport containing the information gathered. For more information on what type of information is gathered using the .bat file and a guide to interpreting the output report, please see the Guide to Interpreting the System Information Batch File article for more details.



For crashes on macOS machines, you may see a dialog with the text FME Workbench quit unexpectedly. If you are able to reproduce the issue reliably, please provide the following information.

1. Crash Report

When an application crashes on macOS, a crash report is automatically generated. You can access this crash report via the ‘Report…’ button on the error dialog.

If you have closed this error dialog, you can also access this crash report using the Console app. You can access this application by typing ‘Console’ in the Spotlight or navigate to Application > Utilities > Console.

When the Console application has been opened, click on ‘User Reports’ on the left menu and this will bring up a list of crash reports. The names of the crash reports will contain the crashed application name and date. Browse through these files looking for one relating to FME.

Once the relevant crash report has been found, please send a copy of the crash report either as a text file or a .crash report when submitting your support case.



For crashes on Linux machines, please provide the following information.

1. Crash Report

By default, when a user experiences a crash on Ubuntu, they are presented with this dialog. This means that Ubuntu has generated a crash report.

Do not check the box that says “Send an error report to help fix this problem”, because it will send not the error report to Safe Software.

The user can find this report in the /var/crash directory. The file extension is .crash and the report name will be the executable path with any forward slash characters replaced by an underscore. Please send the *.crash file when submitting a case.

Was this article helpful?



Please sign in to leave a comment.