Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fatal Error when trying to analyze Textures in 2022.3.1f1 #221

Open
mrdaljama opened this issue Feb 29, 2024 · 2 comments
Open

Fatal Error when trying to analyze Textures in 2022.3.1f1 #221

mrdaljama opened this issue Feb 29, 2024 · 2 comments

Comments

@mrdaljama
Copy link

mrdaljama commented Feb 29, 2024

Whenever I try to analyze 'Textures' of my project, I am always met with a specific bug that tells me I am out of memory, whereas I have 32 GB of RAM which I believe is enough.

Steps to reproduce the behavior:

  1. Window>Analysis>Project Auditor
  2. Click Analyze
  3. Click the "View: Summary" dropdown box and locate Assets>Textures>Textures and click "Ok" on the popup window
  4. After a while, a fatal error will pop out and freeze your system is why I had to take a photo of the issue with my mobile phone instead of screenshot

Expected behavior:
I expected it to go through with no errors and the analysis to be completed

Screenshots:
IMG_20240229_142638

System Information:

  • OS: Windows 11 (10.0.22622) 64bit
  • RAM: 32 GB
  • GPU: RTX 4070
  • Unity 2022.3.1f1
  • Project Auditor 0.10.0
@Kethers
Copy link

Kethers commented Sep 25, 2024

similar issue in Unity 2021.3.29f1, I use auditor for several times and always leads to OOM crash. How is it possible to consume 64G memory with just code and shader analysis? Definitely it has memory leaks somewhere.

@Kethers
Copy link

Kethers commented Sep 26, 2024

similar issue in Unity 2021.3.29f1, I use auditor for several times and always leads to OOM crash. How is it possible to consume 64G memory with just code and shader analysis? Definitely it has memory leaks somewhere.

Project Auditor 0.10.0 causes the issue. Now I use 0.11.0 and this crash disappears, for now.
For 0.10.0 version package, just "add package by name". For 0.11.0 git clone and manually add to manifest.json will be needed as README has said.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants