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

System.OutOfMemoryException #384

Open
M00nBack opened this issue Nov 27, 2024 · 2 comments
Open

System.OutOfMemoryException #384

M00nBack opened this issue Nov 27, 2024 · 2 comments

Comments

@M00nBack
Copy link

M00nBack commented Nov 27, 2024

Description

If too many assemblies are opened, a System.OutOfMemoryException error will be reported when searching, but in fact I still have a lot of free memory that is not used.

@an0ndev
Copy link

an0ndev commented Dec 1, 2024

@M00nBack are you running 32-bit dnSpy instead of 64-bit? 32-bit processes on Windows are still capped at 2GB RAM*

Try using 64-bit dnSpy, you should only need the 32-bit binary for debugging 32-bit processes.

*can be 3GB-4GB depending on different conditions, see https://learn.microsoft.com/en-us/windows/win32/memory/memory-limits-for-windows-releases

@ElektroKill
Copy link
Member

As mentioned, please use the 64-bit version of dnSpy. This allows dnSpy to use all of your available memory. Due to 32-bit addressing limitations, 32-bit dnSpy can only utilize 4GB of RAM.

If this issue still occurs when using the 64-bit version, please provide more exact steps to reproduce the problem. If you are analyzing a specific file(s), upload it here or send it to me at elektrokilldev@protonmail.com.

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

3 participants