-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Profile on M1 mac fails with Bounds error #202
Comments
I'm experiencing this same issue on an M1 Mac on Julia 1.7.1 and 1.8.0 (just released as of this comment), for a completely unrelated code. |
I can't replicate this even though I can obtain what looks like a very similar 2-sample profile. This happens when there is no data to show. (2 snapshots it basically useless, so you wouldn't gain any insight from this even if it worked.) However, we should fix the error. The stacktrace makes it clear that the image that ProfileView is attempting to show is empty, despite your two snapshots. The stacktrace is filtered in the FlameGraphs.jl package, so here's a step in the right direction: data, lidict = Profile.retrieve();
using ProfileView.FlameGraphs
julia> g = flamegraph(data; lidict)
Node(FlameGraphs.NodeData(ip:0x0, 0x01, 1:2))
julia> g.child
Node(FlameGraphs.NodeData(eval at boot.jl:368 [inlined], 0x01, 1:2)) What do you see? I want to point out one likely culprit: https://github.com/timholy/FlameGraphs.jl/blob/b1c547a67ce3e3e2fd143da1c2bd3f47a867759d/src/graph.jl#L161 This is what's responsible for identifying the beginning of the "interesting" part of the stacktrace (all the stuff in |
Same error here too with Julia 1.9.1 on M1 Max. Your code gives: julia> data, lidict = Profile.retrieve();
julia> using ProfileView.FlameGraphs
julia> g = flamegraph(data; lidict)
Node(FlameGraphs.NodeData(ip:0x0, 0x00, 1:1))
julia> g.child
Node(FlameGraphs.NodeData(ip:0x0, 0x00, 1:1)) |
Testing latest master on an m1 mac gives an error while using ProfileView, while normal profiling works fine.
Profile:
ProfileView:
ProfileView version: 1.5.0
The text was updated successfully, but these errors were encountered: