Symptom
- BTP node fails to start a .NET web application and returns a segmentation fault (SIGSEGV).
- Error in logs: “Segmentation fault” with “Exit status 139”.
- GDB output shows: “Thread 1 '...' received signal SIGSEGV, Segmentation fault.”
- The same application runs successfully in a local container.
Read more...
Environment
SAP BTP Cloud Foundry runtime
.NET 9.0 application using binary_buildpack on a Linux-based stack
Product
SAP BTP, Cloud Foundry runtime and environment all versions
Keywords
SIGSEGV, segmentation fault, exit 139, .NET, dotnet, Cloud Foundry, cgroup v2, Ubuntu 24.04, DOTNET_GCTotalPhysicalMemory, crash loop, binary_buildpack, startup crash, linux stack, container memory, gc memory limit , KBA , BC-CP-CF-CRTM , Cloud Foundry Container Runtime , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview