-
-
Notifications
You must be signed in to change notification settings - Fork 104
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
Invalidations and problems with stack traces #409
Comments
Could it be that these invalidations are caused by the definitions of |
Yes, I suspect so. |
|
Fixed by making stacktraces huge. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I don't really know where to report this, so please move it somewhere else.
I had a brief look at load times using Julia v1.9.0-rc1:
This made me suspicious. Thus, I wanted to check whether invalidations are the reason but ran into some problems:
So there are indeed quite a lot of invalidations. However, it's hard to see the full report since something fails. Verbose printing doesn't help:
I suspect TruncatedStacktraces.jl to play a role here, though:
The first four methods do not have many invalidations and can be displayed without problems:
The text was updated successfully, but these errors were encountered: