Comment 9 for bug 1796408

I've found the cause of the error. I'm sorry, but there is a mess in the signal data of the route, which causes the problem. In file w-005626+014367.w there is this block
 Signal (
  UiD ( 12919 )
  FileName ( FSSignal_1C_2VQ.s )
  Position ( -841.867 0.994007 143.205 )
  QDirection ( 0 0.505806 0 0.862647 )
  VDbId ( 4294967295 )
  SignalSubObj ( 00004013 )
  SignalUnits ( 2
   SignalUnit ( 0
    TrItemId ( 0 938 )
   )
   SignalUnit ( 1
    TrItemId ( 0 939 )
   )
  )
 )

and in file w-005627+014367.w there is this block
 Signal (
  UiD ( 11451 )
  FileName ( FSSignal_1C_2V.s )
  Position ( -84.3275 1 911.661 )
  QDirection ( 0 -0.891052 0 0.453902 )
  VDbId ( 4294967295 )
  StaticDetailLevel ( 0 )
  SignalSubObj ( 0000040f )
  SignalUnits ( 2
   SignalUnit ( 0
    TrItemId ( 0 938 )
   )
   SignalUnit ( 1
    TrItemId ( 0 939 )
   )
  )
 )

As you can see, both blocks refer to the same TrItemId's, that is 938 and 939, which is wrong.
By the way in the logfile of OR there are warnings about a good number of other incoherences within the signal data. So, such data should be corrected by the route author.