Search Issue Tracker
Fixed in 2019.2.X
Votes
12
Found in
2017.1.0f3
Issue ID
944603
Regression
No
Memory leak if only one display device is connected when game is using multiple displays
How to reproduce:
1. Open the "DisplayProject_New" project
2. Open the "scene" scene
3. Make sure your computer has only one display device connected
4. Select "Run In Background" in Player Settings
5. Build & Run the project
6. Check the memory usage (memory is leaking faster in user's project)
Actual result: The game's memory usage is increasing all the time.
Reproducible with: 2017.3.0a7, 2017.2.0b9, 2017.1.0p5, 5.6.3f1, 5.5.4p4.
Notes:
When a computer has two or more display devices the leak is not present.
The Unity Profiler doesn't show what is leaking the memory, only "Total Allocated" is growing.
The Canvas that is not shown must have UI elements to reproduce this leak.
------------------------------------------------------------
Fixed in 2019.2.0a8.
-
mayasarii876
Mar 09, 2022 08:36
http://103.56.148.201/
http://103.56.148.201/newmpo
http://103.56.148.201/mpo17
http://103.56.148.201/mpomm
http://103.56.148.201/mpotower
http://103.56.148.201/parisklub
http://103.56.148.201/juraganslot
http://103.56.148.201/mpo500
http://103.56.148.201/mpokick
http://103.56.148.201/mpoyes
http://103.56.148.201/xyzklub
http://103.56.148.201/betmpo
http://103.56.148.201/ogslot88
http://103.56.148.201/hoki777
http://103.56.148.201/mpojuta
http://103.56.148.201/299slot
http://103.56.148.201/mpo188
http://103.56.148.201/mpogacor
http://103.56.148.201/mpo300
http://103.56.148.201/rgo365
http://103.56.148.201/kingdom288
http://103.56.148.201/wigompo
http://103.56.148.201/mpo8899
http://103.56.148.201/mpopelangi
http://103.56.148.201/mpo555
http://103.56.148.201/dutampo
http://103.56.148.201/klik368
http://103.56.148.201/388hero
http://103.56.148.201/19dewa
http://103.56.148.201/mpoxl
http://103.56.148.201/mpoas
http://103.56.148.201/mposun
http://103.56.148.201/qqslot
http://103.56.148.201/mposport
http://103.56.148.201/dewa234
http://103.56.148.201/mesinmpo -
Topher_CGT
Nov 16, 2020 16:15
This is happening in 2018.4.27f LTS version.
-
EduardBosch
Nov 06, 2018 16:10
I'm having the same issue on 2018.2.11f1
I've solved the issue by disabling the second camera in case the second display is not present.
-
RobMalvern
Sep 06, 2018 14:33
I've observed this in 2018.2.4f1
In my case the profiler showed that the memory is being leaked here: Other->MemoryPool->CanvasBatchRenderers
In addition it happens if there is a Camera targeting Display 2 and Display 2 has not been activated.
-
arkano22
May 01, 2018 20:23
Hi there,
Any updates on this? We're developing a multidisplay app, and once we upgraded to 2017.4.1, it leaks memory like crazy and crashes within a couple minutes if not all screens are plugged in. If we disable all cameras that render to any display other than the main one, things work fine.
In the detailed memory profiler, Other->MemoryPool->CanvasBatchRenderers seems to be the culprit: it grows non-stop until the OS kills the app.
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
- Resizing Profiler Module Details panel and releasing mouse button outside Unity doesn't cancel resize
- "Auto-hide gizmos" preference is not saved when reopening the project
- Sampling a custom depth texture on a machine with a GTX 1080 makes object's textures display the wrong color when in Play mode or Player
- Terrain is missing the Hidden/TerrainEngine/Details/WavingDoublePass shader when AssetBundles are built in older Unity Versions
- [Android] URP Project crashes when built on a device with PowerVR Rogue GE8320 GPU
karl_jones
Jan 17, 2019
Hi. We are investigating the bug. For now the workaround is to disable any cameras that are not rendering to a display.