[engmod]

As you can see by the log file, I had been running for some time.

This is a first for me.

Attached File(s)

•  crashtodesktop.txt (5.34K)
  Number of downloads: 24
•  OpenRailsLog.txt (29.63K)
  Number of downloads: 23

[C44-9W]

The exceptions are warnings, and occur well before the crash. There is no exception at the end of the log, and thus no info on the cause of the crash.

[steved]

According to google,

This error is caused by a failed code assertion (Debug.Fail or Debug.Assert) triggered inside the UpdaterProcess.StartUpdate method of Open Rails. Because you are running an Unstable testing version (indicated by the Jenkins build paths), the developers have configured code assertions to intentionally crash the game via Environment.FailFast so they can catch logic bugs during development.This is a developer-level engine crash, meaning there is likely nothing wrong with your computer, but rather a bug in that specific experimental build of Open Rails.

Randy

[C44-9W]

I should have looked at the other attached file too. In case of an assert, the log contains minimal info (it should have the word "Fail:", and if a message was specified the message text).

Here is the code that asserts:

        internal void StartUpdate(RenderFrame frame, double totalRealSeconds)
        {
            Debug.Assert(State.Finished);                             	<-- this assert fails
            CurrentFrame = frame;
            TotalRealSeconds = totalRealSeconds;
            State.SignalStart();
        }

StartUpdate() is called when a preceding update has not yet finished.

I have no idea why that would happen.

[engmod]

The other file is a copy of the event log.

[engmod]

Hi Gents,

This one is the same crash, but different cause.

I run 2 screens,
I run OR full screen,
I have OR running on its own screen, so it loses focus when I am doing something else.
This crash happened when I clicked on the OR screen.

Attached File(s)

•  event_viewer.txt (5.34K)
  Number of downloads: 5

[engmod]

Some new information, and I have a reproduceable crash.

The clipboard may give the reason for the crash.

The log also contains the crash details.

Ok, this is a known problem with the passing path code.
When a Y is across a passing path, this crash happens.
Passing path code needs to be turned off.

This is valid for this one crash only.

Attached thumbnail(s)

• 

Attached File(s)

•  event_viewer.txt (5.34K)
  Number of downloads: 2
•  OpenRailsLog.txt (15.46K)
  Number of downloads: 3

[steved]

Run it by Google Gemini.
It's pretty informative.

Randy

[engmod]

Gents,

Be aware that I do NOT get the crash to desktop with Carlo's fork.

I will work my way through the builds and see what pops up.

[engmod]

Hi Team,

A rerun of the activity from the original post with a later version of the unstable does not produce a crash.

I will let this topic go to the keeper.

[engmod]

A later version of the unstable.

Just after uncoupling some cars.

Attached File(s)

•  eventvwr.txt (5.34K)
  Number of downloads: 4
•  OpenRailsLog.txt (12.66K)
  Number of downloads: 6

[engmod]

If anyone is able to do a debug build to catch this crash, please speak up.
I can handle any large files.

[jsmr]

Quote

Information: Invalid passing path defined for train 39 at section 440 : overlaps with other passing path

Information: Invalid passing path defined for train 39 at section 436 : overlaps with other passing path

Information: Invalid passing path defined for train 39 at section 416 : overlaps with other passing path

Information: Invalid passing path defined for train 40 at section 440 : overlaps with other passing path

Information: Invalid passing path defined for train 40 at section 436 : overlaps with other passing path

Information: Invalid passing path defined for train 40 at section 416 : overlaps with other passing path

Information: Invalid passing path defined for train 42 at section 440 : overlaps with other passing path

Information: Invalid passing path defined for train 42 at section 436 : overlaps with other passing path

Information: Invalid passing path defined for train 42 at section 416 : overlaps with other passing path

Information: Invalid passing path defined for train 43 at section 440 : overlaps with other passing path

Information: Invalid passing path defined for train 43 at section 436 : overlaps with other passing path

Information: Invalid passing path defined for train 43 at section 416 : overlaps with other passing path

Information: Invalid passing path defined for train 44 at section 440 : overlaps with other passing path

Information: Invalid passing path defined for train 44 at section 436 : overlaps with other passing path

Information: Invalid passing path defined for train 44 at section 416 : overlaps with other passing path

Passing paths.....dont work. Crash every time in ORTS.
Once I removed all passing paths in any activity, no more crashes.