You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Library tests intermittently crash with SIGABRT (exit code 134) on linux-x64 when run under the Mono interpreter in the runtime-libraries-interpreter pipeline. Unlike the osx-arm64 crashes (which hit the same tests consistently), the linux-x64 crashes affect a different test each build:
Recurring across multiple builds in the scan window
First build it occurred
Present in builds 1413624 (May 8), 1410559 (May 6). True origin is likely earlier — the pipeline has been failing consistently for at least 5 builds.
Occurrence count
2/4 builds with distinct test failures (different tests each time), plus 1 build where the failure was masked by retry.
Recommended action
This is a systemic Mono interpreter stability issue on linux-x64. The SIGABRT (abort) signal with core dumps suggests a native assertion or heap corruption within the interpreter. Different tests trigger the crash each build, indicating the root cause is in the interpreter runtime rather than any specific test. Investigation should focus on the Mono interpreter's memory management and native code paths on linux-x64.
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
dotnet.github.io
To allow these domains, add them to the network.allowed list in your workflow frontmatter:
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1413624
Pipeline: runtime-libraries-interpreter (definition 330)
Affected leg: linux-x64 Release
Summary
Library tests intermittently crash with SIGABRT (exit code 134) on linux-x64 when run under the Mono interpreter in the
runtime-libraries-interpreterpipeline. Unlike the osx-arm64 crashes (which hit the same tests consistently), the linux-x64 crashes affect a different test each build:System.Threading.Tasks.Parallel.Tests— exit 134System.Net.WebSockets.Client.Tests— exit 134Error Message
{ "ErrorMessage": "Expression: !CREATE_CHECK_STRING(bSmallObjectHeapPtr || bLargeObjectHeapPtr)", "ErrorPattern": "", "BuildRetry": false, "ExcludeConsoleLog": false }Impact on platforms
runtime-libraries-interpreter(def 330) ·linux-x64 Release· exit code 134 (SIGABRT)First build it occurred
Present in builds 1413624 (May 8), 1410559 (May 6). True origin is likely earlier — the pipeline has been failing consistently for at least 5 builds.
Occurrence count
2/4 builds with distinct test failures (different tests each time), plus 1 build where the failure was masked by retry.
Recommended action
This is a systemic Mono interpreter stability issue on linux-x64. The SIGABRT (abort) signal with core dumps suggests a native assertion or heap corruption within the interpreter. Different tests trigger the crash each build, indicating the root cause is in the interpreter runtime rather than any specific test. Investigation should focus on the Mono interpreter's memory management and native code paths on linux-x64.
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
dotnet.github.ioSee Network Configuration for more information.
Note
🔒 Integrity filter blocked 8 items
The following items were blocked because they don't meet the GitHub integrity level.
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter:Report
Summary