AWS Thinkbox Discussion Forums

Deadline Launcher crashing upon start

Hi,

i just discovered a crash of the Launcher when it was started. So far (since upgrading to 7.2.0.10) it only happened this one time.
Here’s the log file entry:

2015-07-22 15:17:12:  BEGIN - CELL-RS-24\render
2015-07-22 15:17:12:  Deadline Launcher 7.2 [v7.2.0.10 R  (f26c85d44)]
2015-07-22 15:17:12:  Launcher Thread - Launcher thread initializing...
2015-07-22 15:17:12:  Launcher Thread - Launcher thread listening on port 17070
2015-07-22 15:17:16:  Exception on Startup: An Unexpected Error Occurred:FranticX.Scripting.PythonNetException: Collection was modified; enumeration operation may not execute.
2015-07-22 15:17:16:     at FranticX.Scripting.PythonNetScriptEngine.a(Exception A_0)
2015-07-22 15:17:16:     at FranticX.Scripting.PythonNetScriptEngine.ExecuteScript(String scriptName, String script)
2015-07-22 15:17:16:     at a.a(String[] A_0)
2015-07-22 15:17:16:  Deadline Launcher will now exit.

Cheers,
Holger

Strange. That exception is rather specific, but I can’t find any code in the Launcher that should be causing this to happen. We’re also apparently losing part of the exception message (the ‘true’ stack trace is missing), which is unfortunate. I’ll make a note to improve the exception messaging in this specific area so that if this keeps happening, we’ll at least get more info about it.

Was the Launcher running as a service when this happened? Also, was it the first time it was run after upgrading to the new beta build? If so, was the client auto-upgraded, or was the Client installer actually run on that machine?

Hi Jon,

it was indeed the first time the Launcher was started after the upgrade to 7.2.0.10. The upgrade was done through the installer. It was not running as a service.

Cheers,
Holger

Gotcha, it sounds like it might’ve been a small bug with the auto-upgrade code manifesting itself. Definitely let us know if this keeps coming up, though.

Do you know which version that machine would have been upgrading from?

We upgraded from 7.1.0.35.
But it was not through auto-upgrade. We ran the installer.

Gotcha; and sorry – I don’t know why but I had read your previous response as “the upgrade was done through the Launcher”. Clearly I need more coffee :slight_smile:

Privacy | Site terms | Cookie preferences