ORTS.Processes.ThreadHangException at ORTS.Viewer3D.Popups.SignallingDebugWindow.GetCacheEntry (X2685, Northeast Corridor V4.0, Pick Em Up)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Open Rails |
Expired
|
Low
|
Unassigned |
Bug Description
Occasionally I have encountered some mysterious crashes that seem to be related to the CTRL-ALT-F11 ("Tracks") key press.
For example, one occurs with Release X2685, the route "Northeast Corridor V4.0" (USA1A) and the activity LCLPIKUP.act ("Pick Em Up").
When the loco is moving in reverse towards pickup #2 at Taphorn Trans, but just before reaching the two switches that lead to the siding that leads to Taphorn, pressing CTRL-ALT-F11 shows the route, then ORTS hangs; it fails to respond, then spontaneously shuts down. The log file is attached. This behavior is reproducible, at least for me, before or after a save.
I have encountered other freezes caused by the "Tracks" key press, but this is one that I have been able to reproduce easily.
summary: |
- CTRL-ALT-F11 Causes hang and spontaneous close + ORTS.Processes.ThreadHangException at + ORTS.Viewer3D.Popups.SignallingDebugWindow.GetCacheEntry (X2685, + Northeast Corridor V4, Pick Em Up) |
tags: | added: crash graphics |
Changed in or: | |
status: | New → Triaged |
importance: | Undecided → Low |
summary: |
ORTS.Processes.ThreadHangException at ORTS.Viewer3D.Popups.SignallingDebugWindow.GetCacheEntry (X2685, - Northeast Corridor V4, Pick Em Up) + Northeast Corridor V4.0, Pick Em Up) |
Further tests -
1.It is not necessary to perform the first pickup, but I think you must wait until the first traffic train has passed - it uses the switch that the player loco will pass over.
2. Going directly to the switches (omitting Pickup #1 and the reversing) and approaching the switches leading to Taphorn cab-first does not crash. So it appears that the direction may matter, but I did not wait for the traffic to pass so this test may not be complete.
Sid P.