I've had one too many computers with less than 1 gig of memory and I will never do it again. IMHO, a computer used for development should be fast and have lots of RAM. I have lots of stuff open when I'm working ... if I have to wait for any length of time for my computer to respond, I get very, very frustrated. The more RAM, the better.

>Is this really related to low memory? I heard before that VS.Net is memory hungry.

I think it truly is memory-related, and I think the reason I've had this happen occasionally is because I will keep Visual Studio running for days at a time without restarting it or rebooting my computer, with lots of compiles going on. I dunno ... like I said, it never causes me problems and usually goes away by itself without me having to shut down Visual Studio.

~~Bonnie





>Is this really related to low memory? I heard before that VS.Net is memory hungry. I guess that you must have at least 1 gig of RAM on your computer so how much memory would really be needed for that monster to work well?
>
>By the way not that I know anything about the .Net world... yet
>
>
>>I get that occasionally, Einar. I usually just ignore it and it goes away eventually. <g> I've never lost anything. If it gets too persistent and doesn't go away after awhile, then I'll go ahead and close and restart VS.
>>
>>~~Bonnie
>>
>>
>>>I have received the following error message from VS2003 today:
>>>An error has occured which the C# compiler is unable to report due to low memory or possible heap corruption. It is recommended that you save all your files, close and restart Visual Studio.
>>>
>>>Has VS2003 ever told anyone else this?
>>>This happends when I am hardcoding a byte array {byte[]) with 41K elements (just for some testing purposes). I've got a feeling it is related to intellisense issues.
>>>
>>>Einar