while trying to debug a different nasty problem I encountered situation, where debugger just stops executing.
I isolated the problem to this:
If you run debug file while having both Slow Step and Execution Trail ON, studio stops the execution process (like on timeouts or breakpoints) when encountering the Pick Activity.
Any other debugging combination works fine (SlowStep, ExecTrail, HighlightElems, LogActivities, ContinueOnErr), just these two options can never be turned on simultaneously, otherwise execution gets forever stuck on the Pick Activity.
Yes I know logMessageActivity is not ideal trigger nor activity. It has been simplified for demonstration purposes.
I am not sure whether this is studio problem or activity problem so feel free to swap the tags, but my guess it’s in the backend of .NET pick+pickbranch implementation since it acts weird in some other (very difficult to describe) situation:
different bug I encountered that might be related to wrong pickActivity implementation
My pickbranch randomly (sometimes every other execution, sometimes every 700th execution) throws uncatchable exception 0xc0000409 or 0xc0000005.
Involved activities I traced the error to: pickActivity and pickBranch and ElementExist.
It took me 3 days of hitting “debug” to replicate/encounter the error the last time so it is extremely hard to prove/demonstrate.
Tested on different computers: win10 (3 different PCs), winServer2016 (Azure); both from Orchestrator (robot) and from Studio (run and debug).
version: Studio Pro 2020.10.2 Community (non-PRO studio doesn’t have ExecTrail option)
run on: win10pro 64bit
Bonus question: If there is some kind of bug bounty program to incentify well documented bug reports?