[ci-scan] Test failure: profiler runtimeasyncapis crashes (Abort trap: 6, exit 133) on interpreter osx-arm64

## Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1572452
Build error leg or test failing: osx-arm64 Checked (OSX.26.Arm64.Open) — profiler/runtimeasyncapis/runtimeasyncapis/runtimeasyncapis.cmd

Pipeline: `runtime-interpreter` (definition 316), branch `main`. The `runtimeasyncapis` profiler test crashes the profilee app on the interpreter legs: the profilee aborts with `Abort trap: 6` and `createdump` writes a core file, so the console never contains `PROFILER TEST PASSES` and `Profiler.Tests.ProfilerTestRunner.FailFastWithMessage` fails the test. The profilee exits 133 (128 + SIGABRT/SIGKILL). Distinct from dotnet/runtime#132941, which is the crossgen2 R2R exit-code-100 "PROFILER TEST FAILED" variant (different pipeline and non-crashing failure). Reproduces across source build 1572452 and follow-up build 1574900.

## Error Details

```
Running test: profiler/runtimeasyncapis/runtimeasyncapis/runtimeasyncapis.cmd

Unhandled exception. System.Exception: Profiler tests are expected to contain the text 'PROFILER TEST PASSES' in the console output of the profilee app to indicate a passing test. Usually it is printed from the Shutdown() method of the profiler implementation. This text was not found in the output above. Profilee returned exit code 133.
at Profiler.Tests.ProfilerTestRunner.FailFastWithMessage(String error)
at Profiler.Tests.ProfilerTestRunner.Run(...)
at RuntimeAsyncApis.Main(String[] args)
runtimeasyncapis.sh: line 468: Abort trap: 6 (core dumped)
[createdump] Crashing thread signal 6 (0006)
```

## Error Message

```json
{
"ErrorMessage": [
"runtimeasyncapis.cmd",
"Profiler tests are expected to contain the text 'PROFILER TEST PASSES' in the console output of the profilee app",
"Profilee returned exit code 133."
],
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}
```

Agentic workflow metadata (ci-failure-scan)

Workflow artifact: ci-failure-scan
Artifact kind: kbe-verification
Verified match count: 4 hits in failure.log

## First build it occurred
Source build [1572452](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1572452); reproduces in follow-up build [1574900](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1574900), where the profiler work items on osx-arm64 legs failed with this signature.

## Duplicate search
Searched open/closed `Known Build Error` issues for `runtimeasyncapis`, `PROFILER TEST PASSES`, and `ProfilerTestRunner`. dotnet/runtime#132941 tracks the crossgen2 R2R exit-code-100 "PROFILER TEST FAILED" case (non-crashing, different pipeline); dotnet/runtime#132844 tracks a `GetObjectGeneration hr=0x80131389` R2R_CG2 variant. Neither matches this interpreter-pipeline `Abort trap: 6` exit-133 crash. No open `Known Build Error` matches.

---
Filed by [`ci-failure-scan`](https://github.com/dotnet/runtime/blob/main/.github/workflows/ci-failure-scan.md) (detection only). [`ci-failure-fix`](https://github.com/dotnet/runtime/blob/main/.github/workflows/ci-failure-fix.md) walks open `[ci-scan]` KBEs and either opens a small fix PR or comments to loop in owners — it never disables the test.

> [!NOTE]
> Generated by the CI Outer-Loop Failure Scanner agentic workflow.

> Generated by [CI Outer-Loop Failure Scanner](https://github.com/dotnet/runtime/actions/runs/33509302092) · opus48 · 776.4 AIC · ⌖ 16.1 AIC · ⊞ 20.7K · [◷](https://github.com/search?q=repo%3Adotnet%2Fruntime+is%3Aissue+%22gh-aw-workflow-call-id%3A+dotnet%2Fruntime%2Fci-failure-scan%22&type=issues)

### Report

|Build|Repository|Test|Pull Request|
|---|---|---|---|
|[1585871](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1585871)|dotnet/runtime|[profiler/runtimeasyncapis/runtimeasyncapis/runtimeasyncapis.cmd](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1585871&view=ms.vss-test-web.build-test-results-tab&runId=43762526&resultId=117759)||
|[1583047](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1583047)|dotnet/runtime|[profiler/runtimeasyncapis/runtimeasyncapis/runtimeasyncapis.cmd](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1583047&view=ms.vss-test-web.build-test-results-tab&runId=43677708&resultId=117682)||
|[1578663](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1578663)|dotnet/runtime|[profiler/runtimeasyncapis/runtimeasyncapis/runtimeasyncapis.cmd](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1578663&view=ms.vss-test-web.build-test-results-tab&runId=43543902&resultId=117589)||
#### Summary
|24-Hour Hit Count|7-Day Hit Count|1-Month Count|
|---|---|---|
|0|0|3|

Start with profiler/runtimeasyncapis/runtimeasyncapis/runtimeasyncapis.cmd and the runtimeasyncapis.sh execution shown in the build log; inspect the failing profilee path and Profiler.Tests.ProfilerTestRunner.Run/FailFastWithMessage diagnostics. Reproduce on osx-arm64 and trace the Abort trap: 6, then confirm the profilee emits PROFILER TEST PASSES and the interpreter leg passes.

Written by the indexing model from the issue text.