You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the flame graph, you can see that there are seven time samples. All of the samples have runif on top of the call stack, as can be seen in the flame graph. In the data viewer, however, there are no entries for runif.
Here's the code. If you run it and there happens to be a <GC> above a runif in the flame graph, then the runif will show up in the data viewer (but the <GC> won't).
@wch not intentional, from what I remember. BTW. Just noticed that switching between horizontal and vertical states is introducing jitter in the UI, not sure if this is already being tracked.
(This is related to #83.) For example, see http://rpubs.com/wch/294546
In the flame graph, you can see that there are seven time samples. All of the samples have
runif
on top of the call stack, as can be seen in the flame graph. In the data viewer, however, there are no entries forrunif
.Here's the code. If you run it and there happens to be a
<GC>
above arunif
in the flame graph, then therunif
will show up in the data viewer (but the<GC>
won't).@javierluraschi Was this behavior intentional?
The text was updated successfully, but these errors were encountered: