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'
Comments (1)
-
vvvvalentin
Mar 05, 2019 06:55
Changing XmlDocument to XDocument in the code fixes the issue.
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
- “Label” name in Sprite Library Editor window lacks character limit causing long names go under the Object Field
- Preview image (screenshot) is not available after capturing snapshot in Memory Profiler
- Crash on UNITY_FT_Stream_ReadAt when changing TMPro properties after unloading an AssetBundle
- Particles spawn at the same position when using raw byte address buffer in VFX Graph
- Decal Shader Graph - Custom vertex interpolators are always 0
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.