I temporarily turned on code complete. (ST 126.96.36.199)
I typed in 'list of ' (space is important, to make it code complete)
This happens consistently.
I do not get this behaviour with ST 188.8.131.52 on another machine.
(Both machines are win2K)
Naturally enough I blame myself for turning on code completion, however, that done, has anyone else noticed this behaviour.
I had seen at least 3-4 silk test crashes while using this feature. I reported them to Segue support with reproducable example code. They fixed them and told me to wait for next hotfix/update release.
Here are 2 situations where I had similar problem.
In both the cases, it is something to do with the compilation of script you are currently typing.
1.) When there are 2 custom classes with same name, silk compilation fails & crashes.
2.) When I do F12 on a method to go to definition of the method (in this case the definition doesn't exist), silk fails to find the definition and crashes.
Everytime I encountered this error, I commented out everything in my script first. Then started uncommenting blocks of code & compile to isolate the issue. I could isolate the issue in all the cases and successfully use this feature.
The issue can also be reproduced if while running a testcase on an agent machine, you try typing anything that will trigger the autocomplete. I've submitted it to Segue and it seems to be a conflict with compiling code (which autocomplete does automatically to enable custom classes, functions and the such) while the agent is doing something else. I am constantly running code while developing, so my solution was to turn autocomplete off until Segue releases a patch that will render autocomplete usable. Also, I just noticed that I can't use <ctrl-f> to find text while a test is running.