Question

Crash Error on a workbench intermittently, related to ucrtbase.dll

  • 5 February 2018
  • 2 replies
  • 6 views

Badge

We have a nightly (in theory) workbench that is transferring data from a SQL Spatial Server into multiple shapefiles (~150). I would say 1 out of 3 times it runs it will reach a certain point (it seems to be random, not any specific place in the workbench) and it will crash. It is always pointing to "ucrtbase.dll" though. I have investigated it fairly thoroughly and I can't pinpoint a reason it is happening. Nothing is showing in the workbench logs indicating the error.

Is there a known issue with ucrtbase.dll?

I do notice that this workbench uses a lot of memory, but why would it work sometimes and not others?

We are using FME Desktop version 2017 on Windows 7, but it was happening in previous versions also.

Crash report


- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Application Error" /> 
  <EventID 
Qualifiers="0">1000</EventID> 
  <Level>2</Level> 
  <Task>100</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2018-02-05T14:08:14.000000000Z" />
  <EventRecordID>412083</EventRecordID> 
  <Channel>Application</Channel> 
  <Computer>DT3011.LumosNet.com</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>fmeworkbench.exe</Data> 
  <Data>2017.7.26.17259</Data> 
  <Data>58b689dd</Data> 
  <Data>ucrtbase.DLL</Data> 
  <Data>10.0.10586.212</Data> 
  <Data>56fa10f1</Data> 
  <Data>40000015</Data> 
  <Data>0008469a</Data> 
  <Data>272c</Data> 
  <Data>01d39a209df709a4</Data> 
  <Data>C:\apps\FME\fmeworkbench.exe</Data> 
  <Data>C:\apps\FME\ucrtbase.DLL</Data> 
  <Data>0151b76a-0a7e-11e8-ba26-005056c00008</Data>
  </EventData>
  </Event>



2 replies

Userlevel 3
Badge +13

Hi @morijlumos, would you be able to submit a support ticket? Please include the workspace, log file, and a Process Monitor log with Operation = Load Image and Process Name contains "fme". This can help us see if any dlls fail to load prior to the crash. Additionally, reference this Q&A; post in the ticket.

The ucrtbase.dll is a good clue but not enough by itself for us to determine what the exact cause of the crash is.

Badge

Hi @morijlumos, would you be able to submit a support ticket? Please include the workspace, log file, and a Process Monitor log with Operation = Load Image and Process Name contains "fme". This can help us see if any dlls fail to load prior to the crash. Additionally, reference this Q&A; post in the ticket.

The ucrtbase.dll is a good clue but not enough by itself for us to determine what the exact cause of the crash is.

No problem. I also saw this section of the log on the latest fail. It happened right before the crash

 

 

2018-02-14 23:05:55| 482.2| 0.0|INFORM|Format Verification>> Is dataset correctly version [Status-Passed]

 

2018-02-15 03:35:56| 494.4| 12.2|ERROR |No Line Symbol font dataset found: drawing line only!

 

2018-02-15 03:38:26| 494.5| 0.1|INFORM|Closing reader on dataset M:\\M4Mapfiles\\03451745.msi

 

2018-02-15 03:38:26| 494.6| 0.0|INFORM|Creating reader for format:

 

 

As you can see it went from 23:05 to 03:38 before the crash

 

 

Reply