Unhandled exception. System.Exception: Profilee returned exit code 139 instead of expected exit code 100

[lewing]

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=567850
Build error leg or test failing: profiler/multiple/multiple/multiple.sh
Pull request: #98351

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": "Unhandled exception. System.Exception: Profilee returned exit code 139 instead of expected exit code 100",
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=567850
Error message validated: [Unhandled exception. System.Exception: Profilee returned exit code 139 instead of expected exit code 100]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 2/15/2024 3:58:36 PM UTC

Report

Build	Definition	Test	Pull Request
572193	dotnet/runtime	profiler.multiple.WorkItemExecution	#98681
571926	dotnet/runtime	profiler.multiple.WorkItemExecution	#98660
571544	dotnet/runtime	profiler.multiple.WorkItemExecution	#98484
570181	dotnet/runtime	profiler.multiple.WorkItemExecution	#98573
570165	dotnet/runtime	profiler.multiple.WorkItemExecution	#98580
570057	dotnet/runtime	profiler.multiple.WorkItemExecution	#97135
569974	dotnet/runtime	profiler.multiple.WorkItemExecution	#97529
569936	dotnet/runtime	profiler.multiple.WorkItemExecution	#91764
569660	dotnet/runtime	profiler.multiple.WorkItemExecution	#98563
569132	dotnet/runtime	profiler.multiple.WorkItemExecution	#98545
568776	dotnet/runtime	profiler.multiple.WorkItemExecution	#98332
568489	dotnet/runtime	profiler.multiple.WorkItemExecution	#98508
568219	dotnet/runtime	profiler.multiple.WorkItemExecution	#98512
567850	dotnet/runtime	profiler.multiple.WorkItemExecution	#98351
567664	dotnet/runtime	profiler.multiple.WorkItemExecution	#98485
567442	dotnet/runtime	profiler.multiple.WorkItemExecution	#98474
565017	dotnet/runtime	profiler.handles.WorkItemExecution

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	16	17

[ghost]

Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=567850
Build error leg or test failing: profiler/multiple/multiple/multiple.sh
Pull request: #98351

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": "Unhandled exception. System.Exception: Profilee returned exit code 139 instead of expected exit code 100",
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=567850
Error message validated: [Unhandled exception. System.Exception: Profilee returned exit code 139 instead of expected exit code 100]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 2/15/2024 3:58:36 PM UTC

Report

Build	Definition	Test	Pull Request
569132	dotnet/runtime	profiler.multiple.WorkItemExecution	#98545
568776	dotnet/runtime	profiler.multiple.WorkItemExecution	#98332
568489	dotnet/runtime	profiler.multiple.WorkItemExecution	#98508
568219	dotnet/runtime	profiler.multiple.WorkItemExecution	#98512
567850	dotnet/runtime	profiler.multiple.WorkItemExecution	#98351
567664	dotnet/runtime	profiler.multiple.WorkItemExecution	#98485
567442	dotnet/runtime	profiler.multiple.WorkItemExecution	#98474

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
4	7	7

Author:	lewing
Assignees:	-
Labels:	area-Diagnostics-coreclr, blocking-clean-ci, untriaged, Known Build Error, needs-area-label
Milestone:	-

[tommcdon]

@davmason would you mind taking a look?

[davmason]

There's a bug in the test, it only waits for 2 profilers to detach before exiting and there are 3 profilers attached. Sometimes the 3rd profiler requests detach after the runtime has exited