Search Issue Tracker
Won't Fix
Votes
1
Found in
2017.4.0f1
2018.3.0a10
2018.3.1f1
Issue ID
1117306
Regression
No
WebGL crash inside GC
How to reproduce:
1. Open the attached "UnityTest.zip"
2. Build and run the project on WebGL
3. Copy 'content' folder from UnityTest/content to the built project folder
4. In the opened browser go to Developer Tools -> Console
5. Several times refresh the 'index.html' page till console will throw ''Crash function"
Actual results: WebGL Player crash
Reproducible: 2017.4.20f2, 2018.3.7f1
Not reproducible: 2019.1.0b4, 2019.2.0a5
Can't reproduce:
2018.3.0a1- 2018.3.0a9, because of "NullReferenceException: Object reference not set to an instance of an object." errors
2019.1.0b4, 2019.2.0a1 - "Crash function" is reproducible, but not crash
2019.2.0a6 - "Build completed with a result of 'Failed'
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
- Crash on ScheduleGenerateTilingShape when modifying PolygonCollider2D path count and setting path vertices
- Crash when a scene is created with LocalPhysicsMode::Physics3D
- [HDRP] Light doesn't bounce off terrains
- Unity Hub opens instead of the Unity Editor when launching a project from a Windows command line if a backslash is added to the end of the project path
- "ParseErrorException" is thrown when parsing a float with a very small value from JSON
Resolution Note:
To work around this problem call Dispose explicitly on XmlNodeList or XmlElementList objects. The finalizer for XmlElementList is implemented incorrectly, as it makes use of another managed object. Finalizers are not allowed access other managed objects, and this issue is exposed on WebGL.