Can anyone interpret the following error report for me please:
Error: System.InvalidOperationException: Collection was modified; enumeration operation may not execute.
at System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource)
at System.Collections.Generic.List`1.Enumerator.MoveNextRare()
at System.Collections.Generic.List`1.Enumerator.MoveNext()
at Orts.Simulation.RollingStocks.MSTSWagon.SignalEvent(Event evt) in E:\Documents\Coding\Jenkins\jobs\Open Rails Testing\workspace\Source\Orts.Simulation\Simulation\RollingStocks\MSTSWagon.cs:line 2539
at Orts.Simulation.RollingStocks.MSTSWagon.UpdateWheelBearingTemperature(Single elapsedClockSeconds) in E:\Documents\Coding\Jenkins\jobs\Open Rails Testing\workspace\Source\Orts.Simulation\Simulation\RollingStocks\MSTSWagon.cs:line 2113
at Orts.Simulation.RollingStocks.MSTSWagon.Update(Single elapsedClockSeconds) in E:\Documents\Coding\Jenkins\jobs\Open Rails Testing\workspace\Source\Orts.Simulation\Simulation\RollingStocks\MSTSWagon.cs:line 1331
at Orts.Simulation.Physics.Train.physicsUpdate(Single elapsedClockSeconds) in E:\Documents\Coding\Jenkins\jobs\Open Rails Testing\workspace\Source\Orts.Simulation\Simulation\Physics\Train.cs:line 1694
at Orts.Simulation.Physics.Train.Update(Single elapsedClockSeconds, Boolean auxiliaryUpdate) in E:\Documents\Coding\Jenkins\jobs\Open Rails Testing\workspace\Source\Orts.Simulation\Simulation\Physics\Train.cs:line 1578
at Orts.Simulation.AIs.AITrain.AIUpdate(Single elapsedClockSeconds, Double clockTime, Boolean preUpdate) in E:\Documents\Coding\Jenkins\jobs\Open Rails Testing\workspace\Source\Orts.Simulation\Simulation\AIs\AITrain.cs:line 666
at Orts.Simulation.AIs.AI.AIUpdate(Single elapsedClockSeconds, Boolean preUpdate) in E:\Documents\Coding\Jenkins\jobs\Open Rails Testing\workspace\Source\Orts.Simulation\Simulation\AIs\AI.cs:line 674
at Orts.Simulation.Simulator.Update(Single elapsedClockSeconds) in E:\Documents\Coding\Jenkins\jobs\Open Rails Testing\workspace\Source\Orts.Simulation\Simulation\Simulator.cs:line 735
at Orts.Viewer3D.Viewer.Update(RenderFrame frame, Single elapsedRealTime) in E:\Documents\Coding\Jenkins\jobs\Open Rails Testing\workspace\Source\RunActivity\Viewer3D\Viewer.cs:line 706
at Orts.Viewer3D.Processes.GameStateViewer3D.Update(RenderFrame frame, Double totalRealSeconds) in E:\Documents\Coding\Jenkins\jobs\Open Rails Testing\workspace\Source\RunActivity\Viewer3D\Processes\GameStateViewer3D.cs:line 128
at Orts.Viewer3D.Processes.UpdaterProcess.Update() in E:\Documents\Coding\Jenkins\jobs\Open Rails Testing\workspace\Source\RunActivity\Viewer3D\Processes\UpdaterProcess.cs:line 128
at Orts.Viewer3D.Processes.UpdaterProcess.DoUpdate() in E:\Documents\Coding\Jenkins\jobs\Open Rails Testing\workspace\Source\RunActivity\Viewer3D\Processes\UpdaterProcess.cs:line 108
at Orts.Viewer3D.Processes.UpdaterProcess.UpdaterThread() in E:\Documents\Coding\Jenkins\jobs\Open Rails Testing\workspace\Source\RunActivity\Viewer3D\Processes\UpdaterProcess.cs:line 74
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
Page 1 of 1
Error Report Help
#2
Posted 15 December 2019 - 06:30 AM
Hi,
I'm fairly sure this is a task synchronisation problem that I've encountered in the past. I have a personal patch for this but it uses "locking" which is discouraged in the design of OR because it can cause bad stuttering in lower power PCs. I have a fairly powerful PC (4 X 4GHZ processor and solid state disks) and thus don't notice any problem with using "locking" in this area. I believe some developers have come up with other methods to cure this problem.
Dennis
I'm fairly sure this is a task synchronisation problem that I've encountered in the past. I have a personal patch for this but it uses "locking" which is discouraged in the design of OR because it can cause bad stuttering in lower power PCs. I have a fairly powerful PC (4 X 4GHZ processor and solid state disks) and thus don't notice any problem with using "locking" in this area. I believe some developers have come up with other methods to cure this problem.
Dennis
#5
Posted 21 December 2019 - 01:14 PM
Bug report here https://bugs.launchp...or/+bug/1857203 .
#6
Posted 22 December 2019 - 08:15 AM
dennisat has provided a patch for this, which I have integrated in OR NewYear MG rev. 46.
#8
Posted 22 December 2019 - 08:39 AM
Not as it is, because it uses a "lock" mechanism which is deprecated by the OR management team.
#9
Posted 01 January 2020 - 01:39 AM
A bug fix for this, based on a try-catch mechanism, is now present in unstable release U2020.01.01-0921.
Page 1 of 1