[GitHub] [incubator-mxnet] leezu commented on issue #17043: Segmentation fault: 11

[GitBox <gi...@apache.org>]

leezu commented on issue #17043: Segmentation fault: 11
URL: https://github.com/apache/incubator-mxnet/issues/17043#issuecomment-594367715
 
 
   Seeing the issue again in http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-gpu/detail/PR-17751/4/pipeline
   
   It's the same pipeline @szha reported as failing above.
   
   That pipeline runs the following build
   
   https://github.com/apache/incubator-mxnet/blob/5cffa744859658d8192041eafcdcfcf176d27482/ci/docker/runtime_functions.sh#L762-L779
   
   The build log associated with the build used for above failing pipeline is http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-gpu/detail/PR-17751/4/pipeline/51, specifically http://jenkins.mxnet-ci.amazon-ml.com/blue/rest/organizations/jenkins/pipelines/mxnet-validation/pipelines/unix-gpu/branches/PR-17751/runs/4/nodes/51/steps/294/log/?start=0
   
   There are a couple of interesting points about this build and failure:
   1) the build is unrelated to llvm openmp, by the nature of our Makefile build not supporting llvm openmp.
   2) the build does not use jemalloc.
   
   So I think we can conclude that the issue is not with jemalloc, but that there is an underlying MXNet bug and building with jemalloc and openmp makes the bug much easier to reproduce.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services