OutOfMemoryException on String.Concat

  • Thread starter Thread starter Anton
  • Start date Start date
A

Anton

Hi,

one of my clients is getting a OutOfMemoryException when String.Concat is called.

The strange thing is, that there is more than 1GB of free RAM.

The client uses a brandnew (1 week old) 3 GHz Core 2 Duo PC with 3GB RAM and Windows XP Pro.

What could the reason of this exception be?

Thanks,
Anton
 
Anton said:
one of my clients is getting a OutOfMemoryException when
String.Concat is called.

The strange thing is, that there is more than 1GB of free RAM.
Click to expand...

Is it trying to build a single string which is too large, perhaps?
Do you know what it's trying to concatenate?
 
Hi,

the code is concating an error message and a filename. So the string shouldn't be to long.

Anton
 
Anton said:
the code is concating an error message and a filename. So the string shouldn't be to long.
Click to expand...

Hmmm... massive amounts of heap fragmentation? I can't think of
anything else off-hand...
 
Hi Anton ,

OutOfMemoryException can be thrown because of two reasons: ran out of
physical RAM, and ran out of virtual memory space(only for x86 system).

Windows is using virtual memory model. Although there may be a lot of
physical RAM, the virtual memory space may not be enough. We should examine
virtual memory counters, such as "Virtual Size" and "Private Bytes" etc...

I would recommend you to download the "Process Explorer" tool from the link
below. Then, you may examine your application process in Process Explorer.
http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx

First, you should added two more columns for the process lists: "Process
Memory"->"Privates Bytes" and "Virtual Size". Please paste the result here
for analysis.(Get the result when your process is crashing)

Also, you may meet the problem below:
"You may receive the "System.OutOfMemoryException" error message when you
view ASP.NET pages on a server that has 3 gigabytes of RAM"
http://support.microsoft.com/kb/820108

The articles below contain a lot of information about how to understand and
troubleshoot the memory issue:
"Identify And Prevent Memory Leaks In Managed Code"
http://msdn.microsoft.com/msdnmag/issues/07/01/ManagedLeaks/default.aspx
"Investigating Memory Issues"
http://msdn.microsoft.com/msdnmag/issues/06/11/CLRInsideOut/default.aspx

Hope this helps.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Ok, if you need further help, please feel free to feedback, thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
 
Hi Anton ,

How about this issue now? Have you managed to resolve this problem using
the resource I provided? If you still need any help, please feel free to
feedback, thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
 
Back
Top