Crash potentially due to using <call>s with the scheduler.

[Selindrile]

As part of the troubleshooting to figure out why my scholar commands were causing crashes, I've done some testing and I've been able to produce crashes with the following addon loaded, with no other addons or plugins loaded except for some variation of this:

_addon.name = 'CrashMeBaby'
_addon.version = '1.No'
_addon.author = 'Selindrile, not that I really want credit for this'

require('luau')

function doCrash()
        --windower.send_command('wait .15;input /ma "Cure" <me>;wait .1;input /p Crash me baby! <call14>')
	windower.chat.input:schedule(.15,'/ma "Cure" <me>')
	windower.chat.input:schedule(.25,'/p Crash me baby! <call14>')
end

doCrash:loop(.5)

I can't get it to reliably crash in any time frame with any specific setup, but without the , I can't seem to cause a crash at all, and while the alone does cause crashes, it seems adding an action to it makes it more likely, and it also seems that the send_command version is less likely to crash... but all permutations that I've tried with s eventually seem to cause crashes, though it's hard to say how long it will take.

[Selindrile]

Update: I was also able to generate a crash with the following, so it may not actually be related to scheduler:

_addon.name = 'CrashMeBaby'
_addon.version = '1.No'
_addon.author = 'Selindrile, not that I really want credit for this'

require('luau')

tickdelay = os.clock() + .1

windower.register_event('prerender', function()
    if not (os.clock() > tickdelay) then return end
    windower.chat.input('/p Crash me baby! <call14>')
    tickdelay = os.clock() + .1
end)

[Selindrile]

Another follow up, after finding out it may not be related to the scheduler, I did some more general testing wondering if it could be a generic Windower or even vanilla issue, I've done a decent amount of testing (well over 2 hours of constant spam) of a loop making macro to be used over and over again with a /party <call> command in it and couldn't get it to crash, so I strongly suspect that it's not specific to scheduler, but it is specific to using <call> with the command handler.