Thread 'Loader Process' has hung;

[apco25]

After last OR update x3523 I now get this error loading any route in OR. Nothing that I'm aware of changed hardware wise on this PC. Anyone else have this occurring otherwise I'm thinking graphics card failure.


This is a log file for Open Rails. Please include this file in bug reports.
------------ ---------- ------------ ---------- ------------ ---------- --------
Date/time = 4/28/2016 9:28:37 AM (2016-04-28 16:28:37Z)
BIOS = Default System BIOS (American Megatrends Inc.)


Error: Orts.Viewer3D.Processes.ThreadHangException: Thread 'Loader Process' has hung; the consistent stack trace is shown below:
at System.Management.IEnumWbemClassObject.Next_(Int32 lTimeout, UInt32 uCount, IWbemClassObject_DoNotMarshal[] apObjects, UInt32& puReturned)
at System.Management.SecuredIEnumWbemClassObjectHandl er.Next_(Int32 lTimeout, UInt32 uCount, IWbemClassObject_DoNotMarshal[] ppOutParams, UInt32& puReturned)
at System.Management.ManagementObjectCollection.Manag ementObjectEnumerator.MoveNext()
at ORTS.Common.SystemInfo.WriteEnvironment(TextWriter output) in e:\Documents\Coding\Jenkins\jobs\Open Rails Testing\workspace\Source\ORTS.Common\SystemInfo.cs :line 56
at ORTS.Common.SystemInfo.WriteSystemDetails(TextWrit er output) in e:\Documents\Coding\Jenkins\jobs\Open Rails Testing\workspace\Source\ORTS.Common\SystemInfo.cs :line 35
at Orts.Viewer3D.Processes.GameStateRunActivity.InitL ogging(UserSettings settings, String[] args, Boolean appendLog) in e:\Documents\Coding\Jenkins\jobs\Open Rails Testing\workspace\Source\RunActivity\Viewer3D\Proc esses\GameStateRunActivity.cs:line 651
at Orts.Viewer3D.Processes.GameStateRunActivity.<>c__ DisplayClass8.<Load>b__3() in e:\Documents\Coding\Jenkins\jobs\Open Rails Testing\workspace\Source\RunActivity\Viewer3D\Proc esses\GameStateRunActivity.cs:line 148
at Orts.Viewer3D.Processes.GameStateRunActivity.Load( ) in e:\Documents\Coding\Jenkins\jobs\Open Rails Testing\workspace\Source\RunActivity\Viewer3D\Proc esses\GameStateRunActivity.cs:line 190
at Orts.Viewer3D.Processes.LoaderProcess.Load() in e:\Documents\Coding\Jenkins\jobs\Open Rails Testing\workspace\Source\RunActivity\Viewer3D\Proc esses\LoaderProcess.cs:line 158
at Orts.Viewer3D.Processes.LoaderProcess.DoLoad() in e:\Documents\Coding\Jenkins\jobs\Open Rails Testing\workspace\Source\RunActivity\Viewer3D\Proc esses\LoaderProcess.cs:line 138
at Orts.Viewer3D.Processes.LoaderProcess.LoaderThread () in e:\Documents\Coding\Jenkins\jobs\Open Rails Testing\workspace\Source\RunActivity\Viewer3D\Proc esses\LoaderProcess.cs:line 109
at System.Threading.ThreadHelper.ThreadStart_Context( Object state)
at System.Threading.ExecutionContext.Run(ExecutionCon text executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

at Orts.Common.ORTraceListener.TraceEvent(TraceEventC ache eventCache, String source, TraceEventType eventType, Int32 id, String format, Object[] args) in e:\Documents\Coding\Jenkins\jobs\Open Rails Testing\workspace\Source\Orts.Simulation\Common\Er rorLogger.cs:line 123
at System.Diagnostics.TraceInternal.TraceEvent(TraceE ventType eventType, Int32 id, String format, Object[] args)
at System.Diagnostics.Trace.TraceError(String format, Object[] args)
at Orts.Common.ORTraceListener.WriteLine(Object o) in e:\Documents\Coding\Jenkins\jobs\Open Rails Testing\workspace\Source\Orts.Simulation\Common\Er rorLogger.cs:line 205
at System.Diagnostics.TraceInternal.WriteLine(Object value)
at System.Diagnostics.Trace.WriteLine(Object value)
at Orts.Viewer3D.Processes.WatchdogProcess.WatchdogTh read() in e:\Documents\Coding\Jenkins\jobs\Open Rails Testing\workspace\Source\RunActivity\Viewer3D\Proc esses\WatchdogProcess.cs:line 132
at System.Threading.ThreadHelper.ThreadStart_Context( Object state)
at System.Threading.ExecutionContext.Run(ExecutionCon text executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

[geepster775]

You might want to try and force it to update again to the latest which is X3535. Any time you click on Options, and then click okay without changing any options, closing the options window again should trigger a ping for any newer updates.

Also, the updater can bomb at times, allowing you to patch what has become a corrupted install. Sometimes it makes sense to get a fresh copy of the latest complete build from https://james-ross.co.uk/projects/or/builds. Just delete everything from your openrails testing directory (except for the documentation folder, keep that) and unzip any build from the linked site.

Updater is not bulletproof, and any time you start getting errors after an update, a fresh install bypassing the updater process should be the first thing to look at.

[apco25]

I suspected a corrupted update. I cleaned out and started fresh and the problem persists....odd

[apco25]

Digging a around I found that unticking the log shape errors is what is causing the problem, triggering OR's watchdog timer to go off and assume thing is wrong. Unticked and some routes load up just fine. I run highly detailed routes which makes me wonder what has changed coding wise that a route is now too big to load?

[baldwin]

Someone else had the same problem that was caused by one shape that had been added to the route. No route so far is too big to load normally, but if there are a large number of shape errors with "log shape errors" enabled, it is the writing of the errors to the log that causes the problem.

If this option is enabled, the full log will show all shape errors found up to the time Watchdog calls a halt to the load process.

[apco25]

I've turned off the log shape file errors... I've had the same activity load and then not load. Either there's a corrupted shape, which the error log isn't telling me or there's a latency problem with the HD my content resides on, or the watchdog timer's wait time has been reduced to a value that's too low loading a big route / activity. I'm going to open a ticket for this.

[Vince]

Reboot your system and then shut down any running processes / applications not needed by the system or Open Rails.
Any Adobe products, Real Audio and Norton AV come to mind. Sort the processes list by your UserID. These are what to look in. Stay away from System UserID stuff unless you're a geek. Anti Virus sometime has a way to pause/disable but pull the internet plug before shutting any AV off.

When using the Task Manager (TM), if you try to shutdown a critical process the TM will issue an 'are you sure?' warning so not to worry about damaging your system.

regards,

edit-add: Route_Riter [CHECK ROUTE] test may be able to find the questionable shape.