.NET (Core and Framework)

14-Jun-07 15:34

Is there a memory allocation limit in .net?

As I recall, in Turbo Pascal no individual allocated block of memory can exceed 64K.
I still see that when I use C (and Borland's compiler).
But it seems .net doesn't have that limit, I've created arrays larger than that and they seem to work fine, until I run out of memory:

byte[] x = new byte [ 0x597FEFCCUL ] ; // Succeeds

but

byte[] x = new byte [ 0x597FEFCDUL ] ; // Throws System.OutOfMemoryException

byte[] x = new byte [ 0x7FFFFFFFUL ] ; // Throws System.OutOfMemoryException

and

byte[] x = new byte [ 0x80000000UL ] ; // Throws "Arithmetic operation resulted in an overflow."

So it appears it's limited to available memory, but no more than 2GB?
Is this documented anywhere?

Don't get me wrong, I'm not complaining, just curious.

Sathesh Sakthivel14-Jun-07 15:46

Sathesh Sakthivel

14-Jun-07 15:46

Memory Allocation[^]

Regards,

Satips. Rose | [Rose]

PIEBALDconsult14-Jun-07 16:08

14-Jun-07 16:08

What's that got to do with .net?

Dave Kreskowiak14-Jun-07 17:09

Dave Kreskowiak

14-Jun-07 17:09

Yeah, Satips hasn't been hitting the mark with a lot of his answers. From what I've seen, he's missing the target entirely.

Every process under 32-bit Windows gets it's own 4GB virtual address space, divided into 2GB for user-mode code/data and 2GB for kernel-mode. This built-in limit is what you're bouncing up against.

You CAN change this limit in the systems boot.ini file to give the user-mode space a 3GB limit, but that's all, no more. The kernel-mode space will get limited to 1GB. There ARE consequences to doing this! Read all the links here[^].

The .NET Framework will support the larger user-mode virtual address space, but it's not recommended on all platforms. I can't seem to find that supported list right now though.

A guide to posting questions on CodeProject[^]

Dave Kreskowiak
Microsoft MVP
Visual Developer - Visual Basic
2006, 2007

PIEBALDconsult14-Jun-07 17:48

14-Jun-07 17:48

Ah, now that's an answer. If only the books I have would at least happen to mention it in passing.

Regular expression not matching as expected

Dave Kreskowiak15-Jun-07 4:41

Dave Kreskowiak

15-Jun-07 4:41

PIEBALDconsult wrote:
Ah, now that's an answer.

A guide to posting questions on CodeProject[^]

Dave Kreskowiak
Microsoft MVP
Visual Developer - Visual Basic
2006, 2007

tgrt14-Jun-07 4:19

14-Jun-07 4:19

I have a regular expression that isn't matching the text into a capture group
as expected. What makes this odd is that it works fine in Expresso, but not
at run-time in the application.

The problem is that the "ErrorMessage" capture has a value of "Error
processing" at run-time; however, in Expresso it has "Error processing
CallRaisesError" which is what I expect.

What am I missing here?

Regular Expression:
\A\d{2}[\s\t]+(?<ErrorMessage>.[^\t]*)[\s\t]+(?:.[^,]*,[\s\t])*(?:.[^;]*;)[\s\t](?<ErrorNumber>\d*)[;][\s\t]+{DONE}\z

Test data:
01\tError processing CallRaisesError\t; 10000; {DONE}

Options:

RegexOptions.Compiled | RegexOptions.CultureInvariant | <br />
RegexOptions.IgnoreCase | RegexOptions.Multiline

PIEBALDconsult14-Jun-07 16:59

14-Jun-07 16:59

I don't know, I'm fairly new to regular expressions as well.

But it doesn't help that the post has an unfortunate smiley in it. You may want to modify the post with the code within a pre block (or whatever the proper term is).

Also, be sure that things like \t are understood by the processor,
you may need to use a literal string (preceeded by an @ sign): "abc\tdef" will be different from @"abc\tdef" and "abc\\tdef".

tgrt15-Jun-07 3:40

15-Jun-07 3:40

Neither the pre or code blocks do anything about the smiley. Apparently, you're stuck with it. I figured it would be easy to ascertain that the winking smiley is a "; )" (just remove the space). The \t is a tab character in C# and is used there as such to illustrate the delimiter in the output.

PIEBALDconsult15-Jun-07 13:49

15-Jun-07 13:49

tgrt wrote:
I figured it would be easy to ascertain that the winking smiley is a "; )"

I didn't know whether or not it was safe to do so.

tgrt wrote:
The \t is a tab character

Yes, but do you want the regex to contain a TAB character or the literal \t?
If the latter (as I expect), then you need to either use a literal string or escape the backslash (\\t).

tgrt15-Jun-07 16:48

15-Jun-07 16:48

PIEBALDconsult wrote:
Yes, but do you want the regex to contain a TAB character or the literal \t?
If the latter (as I expect), then you need to either use a literal string or escape the backslash (\\t).

The purpose of the \t in the regular expression is to match a tab character and the \t in the test data is the illustration of there actually being a tab character (basically the string as you'd see it in the locals window for instance).

The tabs match in the expression without fail. The problem is that when ran as part of my application (exact same regular expression and options as noted) it doesn't match part of the message whereas in Espresso (a regular expression build/test application) it does.

PIEBALDconsult15-Jun-07 19:07

15-Jun-07 19:07

Yes, I understand that.

Let's see...

Fact 1 : The text to be tested contains TAB characters that need to be matched.

Fact 2 : To match TAB characters with a regular expression you specify \t (not an actual TAB character).

Fact 3 : The string produced by the C# statement string s="\t"; will contain a TAB character, not the desired \t (even though the debugger may show it as \t).

Fact 4 : To produce a string in C# that does contain the two-characters \t, use either string s=@"\t"; or string s="\\t";

If that's not the problem, then I don't know what is and I hope someone else steps up.

tgrt16-Jun-07 4:16

Re: Regular expression not matching as expected [modified]

16-Jun-07 4:16

Yes on all accounts. The regular expressions in code are @-quoted. Here's a snippet of the declarations within the factory class (there are other types of messages in different formats that can be received and I use these expressions to identify and parse). You can tell the one that's in issue, because it comes up with the smiley! Smile | :)

private const string _patternReturnDataSet = @"\A\d{2}[\s\t]+(?<Column>\w+[,\t]\d+[,\t]\d*[,\t])+[\n\r\f]+(?<Row>(?:[^,\t\n\r\f]*[,\t])+[\n\r\f]+)*{DONE}\z";
private const string _patternReturnVariant = @"\A\d{2}[\s\t]+(?<Text>.[^\t]*){DONE}\z";
private const string _patternError = @"\A\d{2}[\s\t]+(?<ErrorMessage>.[^\t]*)[\s\t]+(?:.[^,]*,[\s\t])*(?:.[^;]*;)[\s\t](?<ErrorNumber>\d*)[;][\s\t]+{DONE}\z";
private const string _patternInvalidCommand = @"\A(?:\d{2}[\s\t]+)?(?<ErrorMessage>.[^;]*)[;\s\t]+{DONE}\z";
private const RegexOptions _options = RegexOptions.Compiled | RegexOptions.CultureInvariant | RegexOptions.IgnoreCase | RegexOptions.Multiline;

PIEBALDconsult16-Jun-07 5:43

Re: Regular expression not matching as expected [modified]

16-Jun-07 5:43

Huh, alright, now I'm stumped. But I'll try this out myself and maybe learn something.
Fortunately, this latest post also came into my email so I have a no-smiley version of the line to use.

-- modified at 11:52 Saturday 16th June, 2007

Hmmm, I get:

System.Text.RegularExpressions.RegexParser(ScanGroupOpen)parsing "\A\d{2}[\s\t]+(?.[^\t]*)[\s\t]+(?:.[^,]*,[\s\t])*(?:.[^;]*;)[\s\t](?\d*)[;][\s\t]+{DONE}\z" - Unrecognized grouping construct.

-- modified at 12:17 Saturday 16th June, 2007

I added names for the capturing groups (I assume you specified names but used angle-brackets, try apostrophes)

@"\A\d{2}[\s\t]+(?'ErrorMessage'.[^\t]*)[\s\t]+(?:.[^,]*,[\s\t])*(?:.[^;]*;)[\s\t](?'Number'\d*)[;][\s\t]+{DONE}\z"

But it doesn't match... yet.

-- modified at 12:35 Saturday 16th June, 2007

OK, it matches, and misbehaves as described.

-- modified at 12:51 Saturday 16th June, 2007

The missing text is going to the second non-capturing group (I made it capture just to see).

It appears the first group isn't being greedy enough.

-- modified at 13:02 Saturday 16th June, 2007

This
@"\A\d\d\t(?'ErrorMessage'[^\t]*)\t;\s*(?'Number'\d*);\s*{DONE}\z"
works on the sample provided.

-- modified at 13:16 Saturday 16th June, 2007

First, I'll say that \s includes \t, so [\s\t] can be simplified to \s

Other than that, I changed this V from a + to a * and it seems to work
@"\A\d{2}\s+(?'ErrorMessage'.[^\t]*)\s*(?:.[^,]*,\s)*(?:.[^;]*;)\s(?'Number'\d*);\s+{DONE}\z"
I would also remove these ^ ^ ^

PIEBALDconsult16-Jun-07 7:47

16-Jun-07 7:47

Just trying again, to see if I can have the pre tags but no smiley

Other than that, I changed this       V  from a + to a * and it seems to work
@"\A\d{2}\s+(?'ErrorMessage'.[^\t]*)\s*(?:.[^,]*,\s)*(?:.[^;]*; )\s(?'Number'\d*);\s+{DONE}\z"
I would also remove these   ^             ^             ^

I guess not, so I added the SPACE.

tgrt16-Jun-07 13:20

16-Jun-07 13:20

Thanks for all your work on this. I'm stumped too. I hoped that I was missing something obvious.

I'm actually using Regex.Match for the work I'm doing. The capturing groups seem to work fine except for the one mentioned whether I use the < or the '. I cannot get it to match if I leave out the \t -- I wonder why it works for you, are you using the same Regex options that I am? (The \s is in there as well, because the delimiter isn't necessarily always a \t -- it's a crappy legacy system I have nothing to do with.)

So far no luck. This is very odd.

PIEBALDconsult16-Jun-07 17:20

16-Jun-07 17:20

I think the culprit is that +, but I don't know why it would work in one system and not the other.

I am using the same options, and using .Matches to be sure I get only the one match.

tgrt17-Jun-07 5:05