System.NullReferenceException at ORTS.Processes.UpdaterProcess.Update (X.1935)

Bug #1268395 reported by Edward Keenan
34
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Open Rails
Fix Released
High
James Ross

Bug Description

Currently running V1935 and I have been experiencing this error when exiting an activity. This error does not always happen so it is difficult to establish a pattern with this error.

Error: System.NullReferenceException: Object reference not set to an instance of an object.
   at ORTS.Processes.UpdaterProcess.Update()
   at ORTS.Processes.UpdaterProcess.DoUpdate()
   at ORTS.Processes.UpdaterProcess.UpdaterThread()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

Edward K.

Tags: crash
Revision history for this message
Edward Keenan (edwardk) wrote :
Revision history for this message
Rippstein (ch-signale) wrote :

In my case the error appears only by closing with esc+mouseclick in pause-windows on "Quit Open Rails (Alt+F4)"
If I click on the cross right on the top or press Alt+F4 appears no error.
The problem exist sins X1903
look also here:
http://www.elvastower.com/forums/index.php?/topic/23389-screen-pop-up-after-quit/

James Ross (twpol)
summary: - UpdaterProcess Error.
+ System.NullReferenceException at ORTS.Processes.UpdaterProcess.Update
Changed in or:
status: New → Triaged
importance: Undecided → High
tags: added: crash
Revision history for this message
Rippstein (ch-signale) wrote :
Revision history for this message
Rippstein (ch-signale) wrote :

Tags crash.....
It is not really a crash.
If I click in the Error-Window on OK, ORTS show the Menu.
from the menu I can start every activity without any problems.

Revision history for this message
James Ross (twpol) wrote :

We use the 'crash' tag for anything where the error reporting dialog comes up and its an OR bug (if it is a problem with the content, we use the 'content' tag). Since you are exiting, it doesn't affect much but it is still technically a crash to us.

rdamurphy (rdamurphy)
Changed in or:
assignee: nobody → rdamurphy (rdamurphy)
status: Triaged → Fix Committed
Revision history for this message
Rippstein (ch-signale) wrote :

The error does no longer appear in version X1991

Revision history for this message
James Ross (twpol) wrote :

The fix silenced ALL updater process errors, not just this one, so I reverted it. Looking at other options...

Changed in or:
status: Fix Committed → Triaged
assignee: rdamurphy (rdamurphy) → James Ross (twpol)
Revision history for this message
Rippstein (ch-signale) wrote :

Now I get the error again (with X2017), as attatchments the error-information with line-numbers, perhaps it help you.

Revision history for this message
Rippstein (ch-signale) wrote :
Revision history for this message
Rippstein (ch-signale) wrote :
Revision history for this message
Tarcisio (alessandro-licastro) wrote :

Hi, i have the same problem, while i exit the game, appear the message "error" (Object reference not set to an instance of an object).

See log attachements. ;)

Notice: in the log, i used my scenery in wip, but, this error appear the same if i used an other scenery downloaded.

James Ross (twpol)
summary: System.NullReferenceException at ORTS.Processes.UpdaterProcess.Update
+ (X.1935)
James Ross (twpol)
Changed in or:
assignee: James Ross (twpol) → nobody
Revision history for this message
Rippstein (ch-signale) wrote :

Since X2616 I can't observe the System.NullReferenceException any more, if I close the OR by ESC and Mouseclick on the Window "OpenRails beenden (Alt+F4)".
For me the problem is solved with X2616

Revision history for this message
James Ross (twpol) wrote :

Excellent news.

Changed in or:
assignee: nobody → James Ross (twpol)
milestone: none → 1.0
status: Triaged → Fix Committed
Revision history for this message
Walter Niehoff (wniehoff-deactivatedaccount) wrote :

Don't get all exited. Contrary to Rippstein's report, I still get this error in SVN 2622. It's the same as I described in my duplicate report (1348674). Running in debug mode and launching with either Launch or Menu.

Revision history for this message
James Ross (twpol) wrote :

Can you reproduce the error with an automatic build from my site? Do you have any local modifications?

Revision history for this message
Walter Niehoff (wniehoff-deactivatedaccount) wrote :

No local mods, and I could just checkout a new copy. Where is "my site"?

Revision history for this message
Rippstein (ch-signale) wrote :

I have the 2615 from official OR Download
the 2616 and 2622 from your site:
http://james-ross.co.uk/projects/or/builds
I have tested all my routes (most Swiss-Routes, and MSTS official routes) with 2622 but not with all activities
no error in all this cases.

But with one heavy Route I have got this hang-error:
http://www.elvastower.com/forums/index.php?/topic/25374-x2620-error-ortsprocessesthreadhangexception/
The error appears in 2616 at a moment where in 2615 the progress-bar moves very very slow.

Revision history for this message
James Ross (twpol) wrote :

Walter, http://james-ross.co.uk/projects/or/builds - I automatic do a clean release build of each version here.

Rippstein, please could you report the hang-error with details on which routes are most likely to cause it in a new bug, thanks.

Revision history for this message
Walter Niehoff (wniehoff-deactivatedaccount) wrote :

In the process of my latest checkout of #1388861 (3D hardware), I noticed that I got the null exception ONLY after I had toggled 3D off (Ctrl+T). If I did an Esc then click Alt+F4 to exit WITHOUT TURNING 3D OFF, then I got no null exception report. So, I was going to abandon 3D anyway, so I disabled it with Nvidia Control Panel. Result: Now the null exception is SOLID.

I asked myself what could be causing the problem if it was unique to me. I came to suspect the fact that I have a 120 Hz display. I had be running with Vsync off, so I turned it on. Guess what? The null exception problem went away. I was careful to test it a half-dozen times, each time waiting until the frame rate crept up to and settled at 120.

Now, I have no idea how that can turn into a null except when I turn Vsync off and allow it to run as fast as it wants to. However, I see no good reason for me to run with Vsync off.

Revision history for this message
James Ross (twpol) wrote :

Thanks Walter, that's fascinating and quite weird. If you're okay with it, I'll leave the bug report closed and we'll wait and see if other people continue to have this issue.

Revision history for this message
Walter Niehoff (wniehoff-deactivatedaccount) wrote :

Fine with me!

James Ross (twpol)
Changed in or:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.