![]() ![]() When Memory Clean cleans your memory, your already slow system will proceed to get even slower. I would get in the habit of running Memory Clean in such instances rather than having it automatically kick in when memory resources are running low and your system is feeling sluggish. Like Memory Diag, Memory Clean is most effective after you close an intensive app because it cleans up the caches that the application left littered across your Mac that can fragment your memory and slow down performance. So I'm wondering if Unity had JobTempMemoryLeakValidation turned on by default before somehow? I even searched the Editor Log and couldn't find any of the previous warnings.I don't have any scientific or anecdotal evidence to support the following advice, but I would counsel you against enabling Auto Clean. Then I tried turning off JobTempMemoryLeakValidation and, after restarting, all the warning and logs stopped appearing. Allocation of 32 bytes at c001e920 in block 0 (frameIndex=4, lifetime=4, age=2, state=OK) ![]() Number of updated assets reloaded before import = 0 This is what it logged when I randomly clicked on the Custom NUnit folder under Packages in the Project window (copied from Editor Log): Just wanted to relate my experience with them and how they seemed to be triggered by an asset.Ĭlick to expand.I tried clicking on folders and assets in the Project window with JobTempMemoryLeakValidation turned on in 2022.2.1f1 and it started giving some new information in the console. I'm relatively new to Unity and this is way over my head, so I started a new project in 2021 LTS and haven't received any of these warnings (as well as others I was getting in 2022 with Corgi and URP). Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak This will output the callstacks of the leaked allocations. To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This is a leak, and will impact performance Internal: There are remaining Allocations on the JobTempAlloc. ![]() I've tested with both saying yes and no, same end result.Īfter the asset is imported and I click on random items in both the Asset folder and Packages folder, Unity gives these warnings, also seemingly at random: It says some of its source files refer to API that has changed, asks if I want these files updated. When I start with a fresh project (2D URP) in 2022.2.1f1 and click on items in the Project window, no warnings appear. Haven't tested for this warning getting triggered by other assets. I can't find anything in the Corgi forums about it either, though. In my case, it seems to be triggered by the third party Corgi Engine asset after import, which overrides a bunch of project settings and has Package Manager dependencies (not sure if this could cause the issue), hence why I didn't post here. I'm also experiencing this issue in both 2022.2.1f.2.0b12.
0 Comments
Leave a Reply. |