-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Loading a module after workspace() hangs on 0.6+ #22101
Labels
bug
Indicates an unexpected problem or unintended behavior
modules
regression
Regression in behavior compared to a previous version
Milestone
Comments
ararslan
added
bug
Indicates an unexpected problem or unintended behavior
modules
regression
Regression in behavior compared to a previous version
labels
May 27, 2017
Similar on Linux 0.6.0-rc2, except I was able to get a stacktrace showing the cycle: Stacktrace:
[1] _include_from_serialized(::String) at ./loading.jl:157
[2] _require_from_serialized(::Int64, ::Symbol, ::String, ::Bool) at ./loading.jl:200
[3] _require_search_from_serialized(::Int64, ::Symbol, ::String, ::Bool) at ./loading.jl:236
[4] _require(::Symbol) at ./loading.jl:434
[5] require(::Symbol) at ./loading.jl:398
[6] _include_from_serialized(::String) at ./loading.jl:157
[7] _require_from_serialized(::Int64, ::Symbol, ::String, ::Bool) at ./loading.jl:200
[8] _require_search_from_serialized(::Int64, ::Symbol, ::String, ::Bool) at ./loading.jl:236
[9] _require(::Symbol) at ./loading.jl:434
[10] require(::Symbol) at ./loading.jl:398
|
Should be fixed by #21714? |
Yes indeed. Thanks for the reference. |
ararslan
pushed a commit
that referenced
this issue
Jun 1, 2017
* workspace command: fix for missing incremental support * Add a test for #22101
tkelman
pushed a commit
that referenced
this issue
Jun 3, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Indicates an unexpected problem or unintended behavior
modules
regression
Regression in behavior compared to a previous version
I'm seeing this in 0.6-rc2 and current master:
This hangs seemingly indefinitely using 99.9% CPU. Ctrl+C does not interrupt the process; it must be forcibly killed.
It works on 0.5, it just emits a slew of method overwritten warnings rather than hanging.
The text was updated successfully, but these errors were encountered: