Search Issue Tracker
Fixed in 2018.1.X
Fixed in 2017.2.X, 2017.3.X
Votes
0
Found in
2017.1.1p2
Issue ID
952292
Regression
No
Build crashes while closing it with alt+f4 when using .NET4.6
While using Rewired on Unity with Scripting Runtime Version .NET4.6, built project freezes and crashes trying to force close with alt+f4.
To reproduce:
1. Open users attached project "RewiredNet46Bug.zip"
2. Open "Test.unity" scene
3. Make sure that in Player settings Scripting Runtime Version is set to Experimental .NET4.6
4. Build the project for Windows standalone x86_64
5. Open the built project
6. When the project is opened press alt+f4
Expected result: build closes
Actual result: build freezes and crashes
Reproduced on: 2017.1.0a6 2017.1.0b1 2017.1.0b5 2017.1.1f1 2017.1.1p1 2017.2.0f2 2017.3.0a2 2017.3.0a6
Notes: on 2017.3.0b1 2017.3.0b2 crashes instantly on opening built project. After closing the build, Unity editor would often freeze.
The issue does not reproduce if Scripting Runtime Version is .NET3.5
Could not check for regression since .NET4.6 was introduced in 2017.1.0a6
Only reproduces on Windows
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
paragyogi
Oct 15, 2019 04:57
Thanks SUGOIDEV this resolved my issue
Talasas
Sep 27, 2019 05:16
Still seeing this in 2018.3.14. Needed to use workaround.
Enzi
Aug 05, 2018 22:51
@SUGOIDEV
Thank you! Your fix works!
Still not resolved in 2018.2.1f1! All my projects crash with a build unless I used this work around.
monsterbluesHome
Apr 09, 2018 04:30
@SUGOIDEV
Thank you! Your workaround helps with builds made with Unity 2017.3.1p4.
SugoiDev
Nov 22, 2017 18:20
If anyone needs a quick workaround, try add this to a persistent MonoBehavior:
private void OnApplicationQuit() {
if (!Application.isEditor) {
System.Diagnostics.Process.GetCurrentProcess().Kill();
}
}
Remember to flush anything that might not yet have been flushed before doing this, as you're killing the Unity player.