Search Issue Tracker
Duplicate
Votes
4
Found in
2018.3.0a1
2018.3.8f1
2019.1.0a1
2019.2.0a1
Issue ID
1137724
Regression
No
[Crash] Editor crash when calling StreamedBinaryRead::TransferSTLStyleArray
Steps to reproduce:
1. Open User-supplied project ("TransferSTLArrayCrashBug.zip")
2. Press Play and keep pressing "next"
Reproduced in: 2018.3.10f1, 2019.1.0b9, 2019.2.0a9
Not reproduces in: 2017.4.24f*
*Could not run due to compile errors
-
BeatMicrosoft
May 28, 2019 07:42
All platforms crash occasionally, not just editor !!!!!!!!!!!!!!!!!!!!!!!!!!!!
-
zhudianyu
May 24, 2019 10:21
All platforms crash occasionally, not just editor.
-
_Allen
May 05, 2019 07:28
Both Android and iOS platforms crash, a lot of times.
-
KB73
May 03, 2019 21:09
We're seeing this in 2018.2.21f1 a lot - ios 12.1.4, 12.2.0 etc was the last time, on an ipad pro
This is happening with alarming frequency. We're using LZ4 assetbundles..
Crashed: com.apple.main-thread
0 game 0x1025e8f6c void CachedReader::Read<char>(char&, unsigned long) (CachedReader.h:124)
1 game 0x1025e8e68 void SafeBinaryRead::TransferSTLStyleArray<core::basic_string<char, core::StringStorageDefault<char> > >(core::basic_string<char, core::StringStorageDefault<char> >&, TransferMetaFlags) (ContiguousIterators.h:34)
2 game 0x102488500 void NamedObject::Transfer<SafeBinaryRead>(SafeBinaryRead&) (StringStorageDefault.h:35) -
Unity_Joseph
May 03, 2019 18:47
Thank you for reporting. Could you share your source code for creating the ReadArchiveCrashHelper.dll?
-
erkangur
Apr 30, 2019 16:42
I don't know if this is related but I do not use AssetBundles, and still get this crash. It started when I upgraded to 2019.1.0f2.
-
youdingkun
Apr 28, 2019 12:05
This issue also happened on Android device, a lot.
-
G1NurX
Apr 23, 2019 14:51
All platforms crash occasionally, not just editor.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
This is a duplicate of issue #1140019