Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2018.4.X, 2019.4.X, 2020.3.X, 2021.1.X
Votes
2
Found in
2018.4
2019.4
2019.4.21f1
Issue ID
1320358
Regression
No
[Mobile] High crash rates in Loading.PreloadManager
Reproduction steps:
-Due to the nature of this crash, there is no way currently to reproduce it
Reproducible with, according to user reports 2018.4.32f1, 2019.4.17f1, 2019.4.21f1, 2019.4.23f1
Notes:
-Crashes seem to appear after upgrading from 2018.4 to 2019.4
iOS Stacktrace:
0 UnityFramework 0x101bca07c PersistentManager::ReadAndActivateObjectThreaded(int, SerializedObjectIdentifier const&, SerializedFile*, bool, bool, PersistentManager::LockFlags) + 2693812
1 UnityFramework 0x101bca29c PersistentManager::LoadObjectsThreaded(int const*, int, LoadProgress&, bool, PersistentManager::LockFlags) + 2694356
2 UnityFramework 0x101acdcd4 LoadOperation::Perform() + 1660684
3 UnityFramework 0x1017e3edc AssetBundleLoadAssetOperation::Perform() + 1710792
4 UnityFramework 0x101ad03c0 PreloadManager::ProcessSingleOperation() + 1670648
5 UnityFramework 0x101ad0164 operator delete[](void*, std::nothrow_t const&) + 1670044
6 UnityFramework 0x101ad00d0 PreloadManager::Run(void*) + 1669896
7 UnityFramework 0x101b38a08 Thread::RunThreadWrapper(void*) + 2098240
8 libsystem_pthread.dylib 0x1f1c4fc9c _pthread_start + 288
9 libsystem_pthread.dylib 0x1f1c54880 thread_start + 8
Android Stacktrace:
libunity.0x39a304 (PersistentManager::ReadAndActivateObjectThreaded(int, SerializedObjectIdentifier const&, SerializedFile*, bool, bool, PersistentManager::LockFlags) at ??:?)
libunity.0x39a4d0 (PersistentManager::LoadObjectsThreaded(int const*, int, LoadProgress&, bool, PersistentManager::LockFlags) at ??:?)
libunity.0x2d7958 (LoadOperation::Perform() at ??:?)
libunity.0x15df0c (AssetBundleLoadAssetOperation::Perform() at ??:?)
libunity.0x2d9c0c (PreloadManager::ProcessSingleOperation() at ??:?)
libunity.0x2d9a58 (PreloadManager::Run() at ??:?)
libunity.0x2d99c4 (PreloadManager::Run(void*) at ??:?)
libunity.0x336c08 (Thread::RunThreadWrapper(void*) at ??:?)
libunity.0x15059a (Object::SetIsPersistent(bool) at ??:?)
libunity.0x2682d1 (SerializedFile::ReadObject(long long, ObjectCreationMode, bool, TypeTree const**, bool*, Object&) at ??:?)
libunity.0x261e3b (PersistentManager::ReadAndActivateObjectThreaded(int, SerializedObjectIdentifier const&, SerializedFile*, bool, bool, PersistentManager::LockFlags) at ??:?)
libunity.0x261f47 (PersistentManager::LoadObjectsThreaded(int const*, int, LoadProgress&, bool, PersistentManager::LockFlags) at ??:?)
libunity.0x1d5711 (LoadOperation::Perform() at ??:?)
libunity.0xca02b (AssetBundleLoadAssetOperation::Perform() at ??:?)
libunity.0x1d6fe9 (PreloadManager::ProcessSingleOperation() at ??:?)
libunity.0x1d6ec5 (PreloadManager::Run() at ??:?)
libunity.0x1d6e5b (PreloadManager::Run(void*) at ??:?)
libunity.0x21b89b (Thread::RunThreadWrapper(void*) at ??:?)
Comments (2)
-
ertugrulerdogan
Mar 30, 2022 17:18
Loading.PreloadManager related crashes still occurs on 2021.2.17. In our case, crashes seem to appear after upgrading from 2020.3.18 to 2021.2.17.
-
abogarsukov-braingames
May 25, 2021 08:04
Are there any workarounds for this?
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 RaiseException when AddGameElement handles a generic type
- Interpolation 2D results are inconsistent when position.z = position.x is called on Late Update
- Game View's scale slider bar gets set to 2.5x when entering Play Mode
- Crash/Memory leak in a WebGL build when executing a very large switch statement multiple times
- [Asset Bundles] The Active Build Platform is being used instead of the build target to determine material/shader compilation
Resolution Note (fix version 2021.2):
Fix landed in 2021.2.0a19
Resolution Note (fix version 2021.1):
Fix landed in 2021.1.11f1.2629
Resolution Note (fix version 2020.3):
Fix landed in 2020.3.12f1.588
Resolution Note (fix version 2019.4):
Fix landed in 2019.4.29f1
Resolution Note (fix version 2018.4):
Fix landed in 2018.4.36f1