Crashes related to non-existent Arrays

[Chrille]

I sometimes run into this issue where trying to access an array that doesn't exist will crash edrt.exe.

It occurs when I Clear & Destroy and then Re-Create Array objects. This is in order to empty them completely, as just using Clear will keep the old dimensions. Trying to destroy an Array if it doesn't exist will cause this crash. I tried to create two lines of code to avoid this:

Is Array #Objects > 0?:
- Clear Array
- Destroy Array

Is Array #Objects = 0?:
- Create Array

But of course, these events also seem to access the object in a way and thus also cause a crash. This isn't really a major issue as it's easy to keep track of when the arrays need to be destroyed & re-created. I'm just curious as to whether it's a known problem.

[SolarB]

This may be related to how Fusion destroys objects - at the very end of the event loop (http://bugbox.clickteam.com/issues/2016). Does it help if you put those events on separate ticks?

[Chrille]

As in separate "frames"?

[BartekB]

Separate ticks, a tick is where the code gets read then looped back (My definition), so if you do
[Timer is equal to: 1 sec] clear array> destroy array>
[Timer is equal to: 1.2 sec] create array>
Those two events will occur in two different ticks (First one will occur at 60 ticks, second one at 72 ticks if you have set FPS to 60) and will most likely not interfere.

[SolarB]

Thanks for clarifying Snail, it could be related to this.

I meant frames, yeah. I used "ticks" to avoid confusion with Fusion's "frames". You could also do:

tick = 0
-> clear/destroy Array
tick = 1
-> create Array

always
-> add 1 to tick
tick > 1
-> set tick to 0

[Chrille]

I wasn't aware that the array wasn't deleted completely until the end of the cycle and that might indeed be what caused the crash. Thanks for the info and your suggestions!