Welcome to the SRP Forum! Please refer to the SRP Forum FAQ post if you have any questions regarding how the forum works.
I can't replicate this at all but every now again when using search everything dies. Editor exits memory as does OI.
I think that is what happens, next time it happens I'll report what I was doing.
like @jimvaughan noted, it happens when the Find dialog is displayed.
We definately get a crash when closing the dialog. It only happens very irregularly but when it does you know because, as noted, it brings all of OI down.
Still trying to work out the trigger but havent been able to pinpoint anything, let alone with any consistancy...
(Did we use ESC to close or Cancel? Was the previous command a Find Next (or F3) or Find Prev (or F4)? was it just a single search or had multiple searched been executed? did we type in the the string or select text and then Ctrl-F?.....)
I look forward to any other advancement on this! I will post more as I find anything...
To recreate the crash:
I have registered the new OCX anyway. If we experience the Find crash again I will be sure to update this thread.
As always, thanks for the hard work and quick response!
My particular test found 100-odd entries and highlighted them. I even went up and down between a few results too just to replicate real life...
I then replicated it.
Third time for proof (and fourth for that matter ) didnt crash OI....
Open OI. Load SRP Editor.
Open procedure. Find something. Leave find box open.
Open another procdure. run via Command line which triggered my debug.
Realise Find was in my way so close that.
I replicated it straight away. The third time I tried without the debugger (just running a 2nd procedure) but that was fine. Now it seems find again with the debug.
How annoying! It is getting wise to my ways and taking steps to avoid detection....
I have updated to 220.127.116.11 and still crashing.
I am still trying to find a consistent replication for Kevin to weave his magic.
The fact I was able to reproduce easily at least once gives me some hope...
Im not sure of the search term (I can't remember what I was searchin to be honest) but I know I didnt process through the 2nd procedure for the search. I wasn't trying to find a string, I was only trying to trigger the debugger (it was a preset test procedure). Thats why I closed the Find, my mouse was already right there from closing the debugger...
I habitually close the Debugger with the big red X . Just closing (no Abort).
I habitually close the debugger with 'Cancel' although, to be honest, I do ESC it regularly enough. In this case it was definately a Cancel.
I thought I was so close to having a pattern. Turns out not so much :(