|Anonymous | Login | Signup for a new account||2017-03-23 15:15 CET|
|Main | My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001358||Orfeo Toolbox (OTB)||General||public||2017-02-08 12:19||2017-03-10 11:03|
|Summary||0001358: FFT applications random Segfault|
|Description||The dashboard report random segfaults with apTvDomainTransform_fft_shift_fwd on hulk.|
|Additional Information||This problem seems to come from a conflict with MPI and FFTW since removing MPI_FINALIZE nor cleaning the FFTW threads solve (at least partially) reproducible Segfaults.|
From https://github.com/open-mpi/ompi/issues/1364, [^] calling MPI_FINALIZE in a static class destructor could cause segfault on OSX and there is no guarantee in which order the destructors are called at exit.
So the random segfault could occurs when MPI and FFTW cleaning are in different order.
A solution could be to move the call of MPI_FINALIZE outside of the otb::MPIConfig destructor or even to not call MPI_FINALIZE at all since if a process terminates without calling MPI_FINALIZE, independent processes are not affected. Also from the issue : "A much cleaner approach is to not call MPI in your destructor (you're terminating the application anyway)."
|Tags||No tags attached.|
3 otbMPIConfig related test are failing (09/02/2017)
But the FFT segfault dissapear.
Still need to wait few day to see if the random segfault is really removed.
|No more segfault occurs since 2017-03-07 on dashboard.|
|2017-02-08 12:19||Ludovic||New Issue|
|2017-02-08 12:19||Ludovic||Status||new => assigned|
|2017-02-08 12:19||Ludovic||Assigned To||=> Ludovic|
|2017-02-09 09:05||Ludovic||Note Added: 0004018|
|2017-03-10 11:03||Ludovic||Note Added: 0004068|
|2017-03-10 11:03||Ludovic||Status||assigned => resolved|
|2017-03-10 11:03||Ludovic||Resolution||open => fixed|
|Copyright © 2000 - 2017 MantisBT Team|