Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.1.0a6
Issue ID
1098131
Regression
No
[LWRP][Android] ParticlesCollision scene is terminated due to bad Memory Allocation
To reproduce:
1. Open GraphPerf project;
2. Change the Graphics API to OpenGLES2;
3. Build and run ParticlesCollision scene on Android devices.
Reproduced with: 2019.1.0a7 - 2019.1.0a9
Reproduced with LWRP packages: 4.0.1-preview, 4.1.0-preview, 5.0.0-preview
Devices under testing:
Reproduced with:
VLNQA00030, LG G2, 4.4.2, CPU:armeabi-v7a, GPU: Adreno 330
VLNQA00111, Samsung Galaxy J5, 7.1.1, CPU:armeabi-v7a, GPU: Adreno 306
VLNQA00107, Google Nexus 6P, 8.0.0, CPU:arm64-v8a, GPU: Adreno 430
VLNQA00086, Sony Xperia Z4 Tablet, 7.1.1, CPU:arm64-v8a, GPU: Adreno 430
VLNQA00147, Razer Phone, 8.1.0, CPU:arm64-v8a, GPU: Adreno 540
VLNQA00123, Google Pixel 2 XL, 9, CPU:arm64-v8a, GPU: Adreno 540
VLNQA00202, Samsung Galaxy Note 9, 8.1.0, CPU:arm64-v8a, GPU: Adreno 630
VLNQA00144, Samsung Galaxy S9, 8.0.0, CPU:arm64-v8a, GPU:Adreno 630
VLNQA00126, Samsung Galaxy S5 mini (SM-G800F) CPU: Exynos 3 Quad 3470, 6.0.1, GPU: Mali-400 MP,
VLNQA00048, Samsung Galaxy S3 (GT-I9300), CPU: Exynos 4 Quad 4412, 4.3, GPU: Mali-400 MP
VLNQA00178, Xiaomi Redmi Note 4 (Redmi Note 4), CPU: MediaTek Helio X20 MT6797M, 6.0, GPU: Mali-T880
VLNQA00089, Samsung Galaxy Note 10.1 2014 Edition (SM-P600), CPU: Exynos 5 Octa 5420, 5.1.1, GPU: Mali-T628
Not reproduced with:
VLNQA00166, Huawei P20 (EML-L29), 8.1.0, CPU: NOT FOUND, GPU: Mali-G72
VLNQA00103, Samsung Galaxy Note8 (SM-N950F), 7.1.1, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
VLNQA00164, Samsung Galaxy S8 (SM-G950F), 8.0.0, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
VLNQA00175, Samsung (SM-N960F), 8.1.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Resolution Note (2019.1.X):
The fix that would reduce memory-usage has a high chance of causing performance regressions, so we keep the current behavior.