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
This may be quite low priority, since threads are experimental [although they work very well] and deprecations should be fixed. Nevertheless...
Deprecation warnings in threaded code appear to cause segmentation faults. This is much easier to reproduce if JULIA_NUM_THREADS=4, but the error can still occur with JULIA_NUM_THREADS=2. Replacing the deprecated method with its modern counterpart results in no segmentation faults.
using Compat.LinearAlgebra
import Compat.hasmethod
# no Compat.mul! or Compat.LinearAlgebra.mul!ifVERSION.minor ==6 mul! = A_mul_B! endfunctionfoo1()
v =method_exists(Base.sin, Tuple{Float64})
# v = hasmethod(Base.sin, Tuple{Float64})endfunctionfoo2()
A = [1.02.0; 3.04.0]
b = [1.0;2.0]
c = [0.0;0.0]
A_mul_B!(c, A, b)
# mul!(c, A, b)endfunctionfoo3()
v = [1.0;2.0;3.0;4.0]
log(v)
# log.(v)endfunctionbar(f::F) where F <:Function
Threads.@threadsfor i in1:4f()
endendbar(foo1) # sometimes segfaultsbar(foo2) # often segfaults# bar(foo3) # sometimes segfaults on v0.6.3
The text was updated successfully, but these errors were encountered:
This may be quite low priority, since threads are experimental [although they work very well] and deprecations should be fixed. Nevertheless...
Deprecation warnings in threaded code appear to cause segmentation faults. This is much easier to reproduce if JULIA_NUM_THREADS=4, but the error can still occur with JULIA_NUM_THREADS=2. Replacing the deprecated method with its modern counterpart results in no segmentation faults.
The text was updated successfully, but these errors were encountered: