Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.1.X, 2017.2.X, 2018.1.X
Votes
0
Found in
2017.1.0b10
Issue ID
923165
Regression
No
Parental assembly gets unloaded when dynamically loading child assembly from bytes with .NET 4.6
Steps to reproduce:
1. Open attached project
2. Open "AssemblyLoadBug" scene
3. Enter play mode and observe console
*assembly is loaded and its type is successfully retrieved*
4. Exit play mode
*at this moment the main assembly gets unloaded(without forcibly unloading it)*
5. Enter play mode and observe console
Actual result: the main assembly is unloaded and getting its type causes a failure (Editor needs to be restarted)
Notes:
Only reproducible when using Assembly.Load from bytes (alternatively restart Editor, select "AssemblyLoadBug" in the hierarchy and change "Method" value to 'File')
Not reproducible with .NET 3.5 scripting runtime version
Reproducible with: 5.5.0b9, 2017.1.0b1, 2017.1f1, 2017.2.0b1
Fixed in: 2017.1.0p4, 2017.2.0b6, 2017.3.0a3, 2018.1.0b6
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Debug Assertion Failed!" error when launching Windows Dedicated Server Player with Script Debugging enabled
- [Cinematic Studio][3D HDRP] Shader warnings thrown in the Console window when creating a new project with Cinematic Studio template
- Autoplay is triggered on Audio Assets when changing Asset Bundle tags
- Inspector Asset Bundle section has no indication for Variants, AssetBundle is written without a space, and Variant dropdown menu is available without setting the Asset Bundle first
- Graphics.DrawProceduralIndirect and Graphics.DrawProceduralNow silently dropped on DX12
Add comment