Forums Bug Reports on sockclose called twice if slow

if an on sockclose event takes a long time to execute, it will be called twice, possibly leading to errors when the event isn't designed to run twice in a row.


alias test sockopen test www.yahoo.com 80
on *:sockopen:test:{
sockwrite -tn test GET / HTTP/1.0
sockwrite -t test $str($crlf, 2)
}
on *:sockclose:test:{
TestAsk
}
alias -l TestAsk echo 4 -a $?

The use of an alias to use $? is just to make a short, easy-to-understand example.

Confirmed here.

How long a time are you talking about? I couldn't reproduce this (WinXP) so I added a little to the code to show time taken

on *:sockclose:test:{
set -u %testask $ticks
TestAsk
}
alias -l TestAsk echo 4 -a $? - $calc(($ticks - %testask)*.001) seconds.

These are the results, there were no doubleups.
how long? - 10.797 seconds.
a bit longer.... - 19.938 seconds.
shorter - 1.156 seconds.
long enough yet? 27.921 seconds.

I think this is an issue with mIRC allowing $? to be used in the event, the help file makes it very clear that $?/$input can not be used during a script event.

Are you able to reproduce the bug without $? ?

This bug also occured to me when I tested my /sleep and /xrun, that use a COM object to delay mIRC, before submitting them to ms.org. This is the note I eventually added, to inform users of this behavior:

• When calling /xrun from an event, expect error such as the event being called twice. One way around this is creating an alias that contains your commands and calling it from the event via /timer 1 0 <alias>