Crash fill_runtime_generic_context when entering the Play Mode in a specific project

This is partly a problem with user code. the method signature for InitializeOnEnterPlayMode does not match the required signature for InitializeOnEnterPlayMode. To fix it now update the signature to match the documentation https://docs.unity3d.com/6000.0/Documentation/ScriptReference/InitializeOnEnterPlayModeAttribute.html That we crash if the signature is not valid instead of giving a proper error message has been fix

Thank you for reporting a bug to Unity. This issue has been fixed in an upcoming release. We have reviewed the issue carefully, and in this case, the team is unable to prioritize backporting this bug to existing releases. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that a backport may destabilize a release in production. Today we will be closing this port. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

Thank you for reporting a bug to Unity. This issue has been fixed in an upcoming release. We have reviewed the issue carefully, and in this case, the team is unable to prioritize backporting this bug to existing releases. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that a backport may destabilize a release in production. Today we will be closing this port. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

Cancelling this 2023.2 tech release issue since the support for this release has come to end of life. Cancelling this 2023.2 port case does not affect any LTS or Unity 6 Beta/Preview that remain open.

Thank you for reporting a bug to Unity. This issue has been fixed in an upcoming release. We have reviewed the issue carefully, and in this case, the team is unable to prioritize backporting this bug to existing releases. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that a backport may destabilize a release in production. Today we will be closing this port. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

Thank you for reporting a bug to Unity. This issue has been fixed in an upcoming release. We have reviewed the issue carefully, and in this case, the team is unable to prioritize backporting this bug to existing releases. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that a backport may destabilize a release in production. Today we will be closing this port. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.