destroy() bug?

[Stonehouse]

Doing something to help out Pikey which involves despawning aircraft that have landed and then shutdown their engines. I wasn't sure if you could get a engine shutdown event for any other situation than a landed aircraft so built a little script that on a landed event put the unitname in a table and then on a engine shutdown event it checked if the event initiator was one of the units in the table and if so did a Unit.getByName(currentunitname):destroy() on it. It may be I am getting a different flavour of "Bug 27912 - Object.destroy() not functional on world objects" or just that I shouldn't be doing a destroy() in an event handler - I don't know if that is breaching some rule of event handlers. Anyway if I comment out the destroy() the script doesn't crash (doesn't do anything useful either obviously other than spit out some debug messages) but if I leave it in I get a access violation and DCS crashes to the desktop 100% of the time.

 

 

dcs.log entry below and can upload the other crash and dump files if needed:

01267.221 INFO DCS: try to write dump information

01267.222 INFO EDCORE: # -------------- 20151214-123535 --------------

01267.223 INFO EDCORE:

01267.223 INFO EDCORE: # C0000005 ACCESS_VIOLATION at E59EF023 00:00000000

01267.237 INFO EDCORE: 00000000 00000000 0000:00000000

01267.241 INFO EDCORE: E59EF023 0022F1A0 0000:00000000 ?GetPosition@MovingObject@@UEAAAEBVPosition3@@XZ()+23

01267.241 INFO EDCORE: 3FE758B9 0022F370 0000:00000000

01267.242 INFO EDCORE: 3FE5E9D8 0022F3A0 0000:00000000

01267.243 INFO EDCORE: 3FC51E77 0022F590 0000:00000000

01267.244 INFO EDCORE: 3FC8C080 0022F5E0 0000:00000000

01267.244 INFO EDCORE: ED1C72DF 0022F660 0000:00000000

01267.245 INFO EDCORE: ED1C7825 0022F6B0 0000:00000000

01267.245 INFO EDCORE: 3FF20E88 0022F720 0000:00000000

01267.246 INFO EDCORE: 3FF24E72 0022F750 0000:00000000

01267.246 INFO EDCORE: 3FF3B0F4 0022F780 0000:00000000

01267.247 INFO EDCORE: 3FF3B044 0022F7B0 0000:00000000

01267.247 INFO EDCORE: 3FFEA94C 0022FE60 0000:00000000

01267.249 INFO EDCORE: 3FFEDB15 0022FEA0 0000:00000000

01267.255 INFO EDCORE: 77195A4D 0022FED0 0000:00000000 BaseThreadInitThunk()+D

01267.255 INFO EDCORE: 773CB831 0022FF20 0000:00000000 RtlUserThreadStart()+21

01267.440 INFO EDCORE: Minidump created.

01267.440 INFO DCS: try to write track file

 

 

PS Someone else also tried to help him and has reported they hit the same issue but a group level destroy works.

Edited December 14, 2015 by Stonehouse

[Grimes]

Reproduced and reported. Not strictly the same as the other bug since Object.destroy works just fine on units. It appears to be just an issue when you destroy it during the onLand event. Scheduling the destroy call later does not produce a crash.