Use Marshal.InitHandle API to avoid memory leak when OOM happens

[DoctorKrolic]

Fixes: #1430

[jevansaks]

/azp run

[jevansaks]

I checked out this branch locally and started running tests and I see a few test failures -- "GeneratorTests.InterestingAPIs":

Windows.Win32.NativeMethods.g.cs(64,33): error CS1503: Argument 2: cannot convert from 'Windows.Win32.Security.Cryptography.NCRYPT_KEY_HANDLE' to 'nint'

@DoctorKrolic If you can, run tests locally in Test Explorer. Ideally the full set, but the "Full" generation tests can take a long time so I'm ok if you just run the "No Traits" set before putting up a PR:

Click the "Group By" button in task explorer to group by Traits and then run the "No Traits" set:

[DoctorKrolic]

run tests locally in Test Explorer

Is there a apecific reason why CI is blocked here from "untrusted" contributors? I am used to rely on CI to uncover test failures and all repos in dotnet org I worked with have their CI open to any contributor. It seems very inconvinient, that you have to manually trigger CI run every time I make a commit

[jevansaks]

Is there a apecific reason why CI is blocked here from "untrusted" contributors? I am used to rely on CI to uncover test failures and all repos in dotnet org I worked with have their CI open to any contributor. It seems very inconvinient, that you have to manually trigger CI run every time I make a commit

I defer to @AArnott who set up the pipelines. This may be because the pipelines are in ADO and if they were GitHub actions it would be safer to run them automatically? Not sure. It's like this in a lot of repos I work in.

[jevansaks]

/azp run