[ci-scan] Crash: RuntimeAsyncApis profiler test aborts (exit 134/SIGABRT) on runtime-interpreter linux x64/arm64

## Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1578663
Build error leg or test failing: coreclr Pri1 Runtime Tests Run linux x64 / arm64 checked — profiler work item (`RuntimeAsyncApis` profiler test)

KBE authoring guidance (ci-failure-scan)

- `Error Details` is for readers. Paste the full exception, stack trace, or build error excerpt so the failure is understandable without opening the raw log.
- Build Analysis parses only the single JSON block under `Error Message`.
- `ErrorMessage` array entries are matched in order; each is a case-sensitive ordinal `String.Contains` substring copied verbatim from the failing log.
- Set `BuildRetry` to `true` only for a clear infrastructure retry case. `ExcludeConsoleLog` disables Helix console-log scanning.

## Error Details

On the `runtime-interpreter` pipeline (definition 316), the `profiler` runtime-test work item fails on `linux x64` and `linux arm64` (azurelinux.3) because the `RuntimeAsyncApis` profiler test crashes the profilee `corerun` process with `SIGABRT` (exit code 134) instead of printing `PROFILER TEST PASSES`. The profilee aborts immediately after `Profiler::Initialize`, `createdump` writes a core file, and the profiler test runner raises an unhandled `System.Exception` that fails the whole work item.

```
Profilee STDOUT: Profiler.dll!DllGetClassObject
Profilee STDOUT: Profiler.dll!Profiler::Initialize
Profilee STDOUT: [createdump] Crashing thread ... signal 6 (0006)
...
Test failed: 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 134.
Expected: 100
Actual: 134
END EXECUTION - FAILED

Xunit.Sdk.TrueException: 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 134.
at Profiler.Tests.ProfilerTestRunner.FailFastWithMessage(String error)
at Profiler.Tests.ProfilerTestRunner.Run(...)
at RuntimeAsyncApis.Main(String[] args)
```

Observed in source build 1578663 (2026-09-02) and reproduced in follow-up build 1583047 (2026-09-04), so the failure is stable across builds.

## Error Message

```json
{
"ErrorMessage": [
"Profilee returned exit code 134.",
"at RuntimeAsyncApis.Main(String[] args)"
],
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}
```

Agentic workflow metadata (ci-failure-scan)

Workflow artifact: ci-failure-scan
Artifact kind: kbe-verification
Verified match count: both error lines present in source build 1578663 profiler console log (lines 1275/1278) and reproduced (8 hits) in follow-up build 1583047

---

> [!NOTE]
> This issue was filed automatically by the `ci-failure-scan` agentic workflow (AI/Copilot-generated). Mitigation is handled separately by the `ci-failure-fix` workflow.

> Generated by [CI Outer-Loop Failure Scanner](https://github.com/dotnet/runtime/actions/runs/34072178832) · opus48 · 814.4 AIC · ⌖ 20 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=43760418&resultId=119308)||
#### Summary
|24-Hour Hit Count|7-Day Hit Count|1-Month Count|
|---|---|---|
|0|0|1|