Exception of type 'System.OutOfMemoryException' was thrown. #2392
Unanswered
The-Futurist
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I know this has been discussed here before (2018) but I'd appreciate some options. We have a .Net Framework windows service, it uses RestSharp to download zipped CSV data that we eventually import to a database.
The app is stable and mature and been around for like 9 years or so. We are not in a position to move the software to .Net Core. The service is built for 64GB.
These downloadable datasets have been growing for years and in a test yesterday we got this:
The data itself we know, has a size of 1,150 MB, the next largest one has a size of 908 MB and that downloads OK but will likely soon grow to > 1GB so this is a worry for us. Thus is a backbone service that underpins our university's systems.
We have RestSharp v 106.12.0
I read about this this morning and tried it, but the app still fails: gcAllowVeryLargeObjects
Now I'm seeing some ideas from Copilot:
Does that suggestion seem plausible? I'd like an idea before I dive in and spend time on this, Copilot can be misleading sometimes or just plain wrong.
Beta Was this translation helpful? Give feedback.
All reactions