René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Updating to .net10.0 (from net8.0) Switcher with ChakraCore now causes containers to exit unexpectedly","articleBody":"### The issue\n\nI have been running .net 8.0 for years on AWS ECS without issue. I have updated to net 10.0 just updated the packages that were required as per the upgrade instructions excluding entity framework.\n\n`dotnet outdated -mv 10.0 --exclude pomelo --exclude entity --include Microsoft.AspNetCore --include Microsoft.Extensions --include System.Net.Http.Json --include system. -u\n`\n\nI'm now periodically getting containers that are exiting on AWS with \"Exit code: 139.\" where it logs a single line and then the container becomes unresponsive and shortly afterwards deprovisioned. Apparently 139 is a SIGFAULT or error accessing memory?\n\n`\"terminate called after throwing an instance of 'Js::JavascriptException`.\n\nI'm running it in AWS ECS as `root` and using ` mcr.microsoft.com/dotnet/sdk:10.0` as the base image.\n\nI'm not sure that I'm doing anything exotic. I'm using ReactJS.net which is an older library and it uses Chakracore-linux which is what handles Javascript, but why would it have an issue every now and again just cause it's a new version of .NET?\n\nI'm building it within codepipeline using docker build.\n\nUnfortunately this is stopping me from upgrading to .net10.0. I have a feeling it's something to do with Chakracore to generate SSR react. Grok says switch to `Jint` of V8, not sure if that's the answer here just cause I've updated to .net10 and new docker base images.\n\nOf note, Microsoft have switched form Debian to Ubuntu, will this be an issue? \n\nThanks in advance for any insight from anyone.\n\n\u003cimg width=\"1227\" height=\"217\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/87daa9c9-9485-485d-8f18-4ce004eae180\" /\u003e\n\n### Which .NET image(s) are you using?\n\n mcr.microsoft.com/dotnet/sdk:10.0\n\n### Steps to reproduce\n\nBuild using docker file, push to AWS ECR an deploy to ECS. Website has heavy traffic. This is my docker file:\n\n\n```\nFROM mcr.microsoft.com/dotnet/sdk:10.0 AS build-env\nEXPOSE 80\nWORKDIR /app\n\n# Copy csproj and restore as distinct layers\nCOPY *.sln .\nCOPY MySite.WebUI.Core/*.csproj ./MySite.WebUI.Core/\n\nRUN dotnet restore\n\n# Copy everything else\nCOPY . ./\n\nFROM 369074612400.dkr.ecr.us-east-1.amazonaws.com/node:20.11.1-buster as node-env\nWORKDIR /app\n\n# Run webpack\nCOPY --from=build-env /app ./\n\nWORKDIR /app/MySite.WebUI.Core\nRUN npm ci\nRUN npm run release\nRUN ls -R -1 ./wwwroot/dist\n\nFROM mcr.microsoft.com/dotnet/sdk:10.0 AS second-build-env\nWORKDIR /app\nCOPY --from=node-env /app .\nRUN dotnet publish MySite.WebUI.Core -c Release -o out\n\n# Copy static files to S3\nFROM 369074612400.dkr.ecr.us-east-1.amazonaws.com/amazon/aws-cli:2.15.28 AS copy-static-content-env\nARG AWS_DEFAULT_REGION\nARG AWS_CONTAINER_CREDENTIALS_RELATIVE_URI\nARG AWS_SECRET_ACCESS_KEY\nARG AWS_ACCESS_KEY_ID\nARG AWS_SESSION_TOKEN\nWORKDIR /app\nCOPY --from=second-build-env /app/out ./out\nRUN ls -1 -R ./out/wwwroot/dist\nRUN aws s3 cp ./out/wwwroot/dist s3://MySitelive/dist --recursive\n\n# Build runtime image\nFROM mcr.microsoft.com/dotnet/aspnet:10.0 AS website\nWORKDIR /app\nENV ASPNETCORE_HTTP_PORTS=80\nCOPY --from=copy-static-content-env ./app/out .\nUSER root\nCMD [\"dotnet\", \"MySite.WebUI.Core.dll\"]\n```","author":{"url":"https://github.com/coultonluke","@type":"Person","name":"coultonluke"},"datePublished":"2026-06-12T09:02:35.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":13},"url":"https://github.com/121/JavaScriptEngineSwitcher/issues/121"}