I ran estudio from within a workbench estudio, opened the sample graphical
application and did repeated Step into Routine operations with Auto Expressions
turned on.  There were several "Compiler error" exceptions while evaluating
auto expressions, which I believe is normal when an expression cannot be
evaluated.  However, there was also a precondition violation when trying to 
evaluate the auto expression `l_item' in {EV_NOTIFY_ACTION_SEQUENCE}.has.
The precondition with tag `a_context_class_valid' of
{FORMAL_A}.is_multi_constrained was violated.  The first part of the
precondition was `a_context_class.is_generic', which was False because
`a_context_class.generics' was Void.

I have attached the stack trace when the precondition violation occurred.
I suspect this may be the cause of the one known remaining crash when 
stepping with Auto Expressions on (at least, the only one I know about).

If it isn't obvious what the problem is and you need to investigate further,
you can reproduce the problem quickly (running estudio from within a workbench
estudio), by doing the following:

1. Compile sample graphical application (I did not use a precompile).
2. Run estudio from within a workbench estudio and open this project.
3. Put breakpoint on {EV_NOTIFY_ACTION_SEQUENCE}.has.
4. Click Start to run sample graphical application.
5. When execution stops at breakpoint, turn on Auto Expressions in Watch tab.
   Then click Step by Step 3 times.  Workbench estudio stops with
   precondition violation in {FORMAL_A}.is_multi_constrained.