Crash accessing AppArgs after SetDeviceWindow

Monkey Forums/Monkey Bug Reports/Crash accessing AppArgs after SetDeviceWindow

Peeling(Posted 2016) [#1]
Can't reproduce this in a small test app, but in our game I'm getting a memory access violation if I refer to 'AppArgs' after using SetDeviceWindow. Prior to calling SetDeviceWindow, AppArgs works fine.

Specifically, I was using:

for local i:=0 until AppArgs.Length
if AppArgs[i].Compare(s) <- crashes

I've ended up copying the result of AppArgs into my own array and referring to that, but it's definitely a concern that all is not well somewhere.


marksibly(Posted 2016) [#2]
Odd...can't reproduce it here either, but probably a case of premature GC. Will look into it.