StackTraceArguments are set to be from a global context too often in some cases

When using the flag -simplejitafter:1 (or flags that imply it), it is possible for stack frame argument type information to be marked as having a global caller for every frame. This is most easily visible in debugging output; functions with global callers are printed in backtraces without any arguments (or the simple "()" to indicate no arguments). The cause is likely something in how jitted functions construct stack frame objects.