W^X on Mac for EF Core tests is very slow

Open
#117,754 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp, macos
Domain
operating-systems, performance, testing-qa

Research direction

Start with the Mac EF Core test runs on Helix and the linked build log, then compare the runs with and without COMPlus_EnableWriteXorExecute=0. Review the W^X workaround from #70758 and the EF Core PR #36243. Done means identifying the cause of the timeout and restoring test runs to their expected under-60-minute duration.

Written by the indexing model from the issue text.

Description

area-VM-coreclr tenet-performance

EF Core was running on Mac with W^X disabled (COMPlus_EnableWriteXorExecute=0) because of #70758. Removing the COMPlus_EnableWriteXorExecute now makes the test run extremely long - usually tests on Helix (where this was applied) run in under 60 minutes. With COMPlus_EnableWriteXorExecute=0 removed these did not finish within the timeout of 3 hours (detail).

The PR that removes the W^X workaround: https://github.com/dotnet/efcore/pull/36243.

Dominant language
C#
Stars
18.3k
Forks
5.6k
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/runtime

All issues in dotnet/runtime

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.