Stonkie
Well-known member
- Joined
- Sep 12, 2007
- Messages
- 279
- Programming Experience
- 1-3
I have a pretty large dataset. Sometimes, when I modify it and try to compile, I get a full list of compile errors. The first one is "Custom tool error : System.OutOfMemoryException" and the rest are caused by my DataTables not existing.
I can simply restart the editor, go back in my dataset and drag something (just so it has to save), compile again and all is fine. But this remains quite the annoyance bacause it happens regularly. I have plenty (2GB) memory on the machine and I was at 1.2GB used in the task manager this time, so I am not actually running out of memory. I am on a x86 Windows XP.
I cannot split the Dataset into smaller parts right now (which would make sense in terms of my application design as well) because we are a few months away from release. I am guessing there is a limit to the amount of RAM VS allows its custom tools to take, or maybe some other limit. Is it possible to increase it? Anyone has found a workaround for this?
I can simply restart the editor, go back in my dataset and drag something (just so it has to save), compile again and all is fine. But this remains quite the annoyance bacause it happens regularly. I have plenty (2GB) memory on the machine and I was at 1.2GB used in the task manager this time, so I am not actually running out of memory. I am on a x86 Windows XP.
I cannot split the Dataset into smaller parts right now (which would make sense in terms of my application design as well) because we are a few months away from release. I am guessing there is a limit to the amount of RAM VS allows its custom tools to take, or maybe some other limit. Is it possible to increase it? Anyone has found a workaround for this?
