Closed lkuper closed 8 years ago
It also seems to be happening on Travis: https://travis-ci.org/IntelLabs/ParallelAccelerator.jl/jobs/89117763#L221
This couldn't have anything to do with updating to version 0.5.0 of Images.jl, could it? opt-flow/image.jl is just a small library of image manipulation functions with no dependencies.
I don't see what that code has to do with Images.jl---you're calling a base I/O method on types defined in base (two Matrix{Float32}
and a string). So Images.jl seems unlikely to be the culprit. But do let me know if you discover evidence to the contrary.
The "big change" in Images 0.5 is just a code reorganization, moving I/O into separate repositories. Images.jl itself no long makes any ccall
s---it's now a pure-julia package. So any segfaults are either a bug in julia itself, a bug in a package used by Images, or a bug here.
Nothing new to report, just noting that this is still happening and it worries me. I'll try to investigate later. https://travis-ci.org/IntelLabs/ParallelAccelerator.jl/jobs/89505881#L287
It is confirmed not to be the change in Images library, but the recent commit by @DrTodd13 that changed j2c-array C++ class. We'll have a solution soon.
@ninegua Thanks for investigating!
Nice job finding the source.
It looks as though the segfaults have been fixed now (although we're still getting failures on Travis due to an unrelated issue). I think we can close this. Thanks, @ninegua and @DrTodd13.
I'm intermittently seeing this error:
Line 132 of opt-flow/image.jl is a call to Base.write(). This is against Julia 0.4.0 release on Ubuntu. I see memory usage increase while I'm running but I don't run out of memory before it crashes.