title: AWS Lambda Chalice Layers Segmentation Fault
body: <p>I am deploying a Python 3.7 Lambda function via Chalice. Because the code with its environment requirements, is larger than 50 MB limit, I am using the &quot;automatic_layer&quot; feature of Chalice to generate the layer with the requirements, which is <code>awswrangler</code>.</p>
  <p>Because the generated layer is &gt; 50 MB, I am uploading the generated <code>managed-layer-...-python3.7.zip</code> manually to s3 and create a Lambda layer. Then I re-deploy with chalice, removing the <code>automatic_layer</code> option and setting the <code>layers</code> to the generated ARN of the layer I manually created.</p>
  <p>The function deployed this way worked OK for a couple of times, then started failing occasionally with &quot;Segmentation Fault&quot;. The error rate increased shortly and now it is failing 100%.</p>
  <pre><code>Traceback:
  
  &gt; OpenBLAS WARNING - could not determine the L2 cache size on this system, assuming 256k
  &gt; START RequestId: 3b98bd4b-6cda-4d21-8090-1a49b17c06fc Version: $LATEST
  &gt; OpenBLAS WARNING - could not determine the L2 cache size on this system, assuming 256k
  &gt; END RequestId: 3b98bd4b-6cda-4d21-8090-1a49b17c06fc
  &gt; REPORT RequestId: 3b98bd4b-6cda-4d21-8090-1a49b17c06fc Duration: 7165.04 ms Billed Duration: 7166 ms Memory Size: 128 MB Max Memory Used: 41 MB
  &gt; RequestId: 3b98bd4b-6cda-4d21-8090-1a49b17c06fc Error: Runtime exited with error: signal: segmentation fault (core dumped)
  &gt; Runtime.ExitError
  </code></pre>
  <p>As <code>awswrangler</code> itself requires boto3 &amp; botocore, and they are already in the Lambda environment, I suspected that there might be a conflict of different versions of boto. I tried the same flow by explicitly including boto3 and botocore in the requirements but I am still receiving the same segmentation fault error.</p>
  <p>Any help is much appreciated.</p>