Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.29f1
2022.3.11f1
2023.3.0a8
Issue ID
UUM-50991
Regression
No
Sprite Atlas remains loaded in memory after scene change or unloading assets
Sprite Atlas remains loaded in memory after scene change or unloading assets
Repro steps:
- In attached project, open SampleScene and enter Playmode, use Frame Debugger to observe sprites in scene referencing atlas textures
- Using Memory profiler capture, observe atlas Texture2D reference in memory
- Press 'Space' to open empty scene, press '1' to unload all unused assets or '2' to unload all atlases
- Using Memory profiler capture, observe atlas Texture2D reference is still in memory
Expected results: Sprite atlas and atlased textures should not be in memory after switching scene or being unloaded
Actual results: Sprite atlas and atlased textures remain in memory after switching scene or being unloaded
Test platforms: Windows 11
Comments (83)
-
mateoowen44
Jul 26, 2025 22:34
A few weeks ago, I received an email that claimed I had won a staggering $2 million Bitcoin giveaway sponsored by Binance. At first glance, the message appeared legitimate. It featured official logos, polished wording, and a link that redirected me to what seemed to be Binance’s real website. Everything looked perfect: the login page was professional, there was a security padlock indicating a secure connection, and even the URL was almost identical to the actual Binance site.Caught up in the excitement of what I thought was a lucky break, I entered my credentials without a second thought. When prompted, I also provided my recovery phrase to "verify eligibility." It was a decision I would soon regret. Within minutes, I received a sinking feeling in my stomach as I realized that my entire cryptocurrency portfolio had been wiped out. It wasn’t just my Bitcoin (BTC) that was gone; the scammers had drained everything, including my Dogecoin (DOGE), Cardano (ADA), and Bitcoin Cash (BCH).The realization hit me hard, and I felt utterly sick. I had always prided myself on being cautious and knowledgeable about online scams, but the fake site was so convincing that I had let my guard down. After hours of panicking and feeling helpless, I knew I had to take action. I began searching for help and stumbled upon PRO WIZARD GIlBERT RECOVERY, a team that specializes in crypto scam investigations to recover my lost assets, I reached out to them, sharing my experience and the details of the scam. The team was incredibly supportive and knowledgeable, guiding me through the recovery process step by step. They explained how they could trace the transactions and work to recover my stolen funds. With their expertise, I felt a glimmer of hope.After two days of diligent work, I was ecstatic to learn that I had recovered 90% of my cryptocurrency. The relief was overwhelming, and I couldn’t believe that I had managed to reclaim what I thought was lost forever. I now understand that even the most convincing emails can be traps, and I will always double-check before taking any action in the future.
CONTACT INFO=====WhatsApp +1 (920) 408‑1234
TELEGRAM======:http s:// t. me/Pro_Wizard_Gilbert_Recovery
EMAIL==========:pro wizard gilbert recovery (@) engineer. com
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
In playmode, it is expected to have Texture2D and SpriteAtlas references in memory even if they are referenced in other scenes
Outside playmode, SpriteAtlas references in memory are expected but in itself consumes very little memory (a few properties and references) usually in KBs. The editor's memory profiler might show larger memory used due to the Editor window itself and other editor objects that use extra memory