the simulation often crashes

[cangokalp]

which version of unreal engine is more stable, currently my simulation often crashes sometimes after thousand training episodes sometimes sooner, sometimes I get this error:
Exception thrown at 0x00007FFCE379B540 (UE4Editor-Core.dll) in UE4Editor.exe: 0xC0000005: Access violation reading location 0xFFFFFFFFFFFFFFFF.
and sometimes it just says Blocks stopped working.

[JeremyBYU]

I havent had a crash yet. I am running on Windows 10 using UE 4.16 as recommended here. However I havent run longer than 30 minutes. I pulled from master about 2 weeks ago and built.

[sytelus]

I've started noticing one crash scenario and traced to potential issue in rpclib so I've filed issue there. This is when client sends command but disconnected before command finishes execution. However I'm not sure if your issue is same. I would suggest to try to create some minimal scenario with AirSim so crash can be reproduce. If you run from source code that would help as well to see the call stack and location of the crash.

[cangokalp]

I was suspicious about the blocks environment, so I created a new very basic environment - but still got the error:
Unhandled exception at 0x00007FF7850161AE in Quadcopter.exe: 0xC0000005: Access violation reading location 0xFFFFFFFFFFFFFFFF

What's causing this? Error changes from time to time but it's similar to this usually

[sytelus]

What are the repro steps?

[Kjell-K]

@sytelus @cangokalp I think we are still taking about the same issue #631.
Any solutions yet? This issue stands in the way of performing long time simulations for reinforcement learning. Note that I never had this issues with the AirSim version from early October. Here I was running simulations for 4 days.

Assumption: Error is produced by client.reset(). This error always occurs directly when doing the reset call or directly afterwards when trying to move after reset. Also the client.reset is the major update and change towards the early October version.

[sytelus]

I think latest version should fix this. Lets continue discussion here anyway: #631