PublishReadyToRunComposite and PublishSingleFile are making app crash

[hez2010]

Description

If an app is published with both PublishReadyToRunComposite and PublishSingleFile enabled, the app will crash at startup in silence.

Repro steps:

dotnet new console
dotnet publish -c Release -r win-x64 /p:PublishReadyToRun=true /p:PublishReadyToRunComposite=true /p:PublishSingleFile=true

And run the published single-file app, you will find the app is crashing at startup.

I guess it may be caused by the .r2r.dll file lookup failure.

Configuration

.NET 6 Preview 6

Tagging subscribers to this area: @agocke, @vitek-karas, @VSadov
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Description

If an app is published with both PublishReadyToRunComposite and PublishSingleFile enabled, the app will crash at startup in silence.

Repro steps:

dotnet new console
dotnet publish -c Release -r win-x64 /p:PublishReadyToRun=true /p:PublishReadyToRunComposite=true /p:PublishSingleFile=true

And run the published single-file app, you will find the app is crashing at startup.

Configuration

.NET 6 Preview 6

Author:	hez2010
Assignees:	-
Labels:	area-Single-File, untriaged
Milestone:	-

[hoyosjs]

cc: @dotnet/crossgen-contrib

[VSadov]

Thanks for reporting the issue. It looks like the same bug as described in #45277

It was fixed in #53739, but that fix was too late to be included in Preview 6

[mangod9]

can we ensure this is fixed in preview7. Since #45277 was recently reopened want to ensure things are in fact working correctly.

[VSadov]

@mangod9 There were no recent changes directly affecting composite r2r support in singlefile. So far I am unable to reproduce the test failure that caused reactivation of #45277. I think it could be caused by some temporary condition present in the integration test pass or by some indirect issue that was fixed since then. (any fixes/changes in crossgen ?)

It would be nice to be certain of what caused the failure, but as far as I can see composite r2r works in sdk/main and should work in Preview7.

[mangod9]

Ok thanks for checking, can we try enabling the sdk test then? There were some w^x fixes which might have resolved the issue possibly

[VSadov]

@mangod9 - PR to reenable the test dotnet/sdk#18945
I have tried a few changes as well, like intentionally forcing a failure - to see if the test behaves deterministically.

[agocke]

We can't seem to get this to repro any more -- closing for now, will reopen if it pops again.