Virtual Memory and Thread Stacks

re: Virtual Memory and Thread Stacks

Doug B — Tue, 31 Jan 2006 15:25:43 GMT

This is stunning! I've been hearing of products having trouble with app installs and driver loads on Windows Mobile 5. It was looking like a Merlin redux.

I can't imagine anyone actually depending on the 1 Meg stack this soon after the release VS 05. I'd change the default back to 64 K in a service pack asap. The only worry would be MFC and ATL apps. Perhaps the new port needs the larger stack. That'd take a bit of testing to see if they deal with in a 64 K stack.

Thanks for this info.

Doug

re: Virtual Memory and Thread Stacks

B. Lee — Wed, 08 Feb 2006 08:04:32 GMT

Welcome back, John.
To answer your question, I work on applications that use lots of threads but the default 64K is good enough.

After reading your post, I've checked the 'Stack Reserved Size' on my projets.
It was just a quick test, so I'm now sure how correct(?) this may be
but here are my observations.

1. Created a Smart Device project with hello window code for WM5.0 in VS2005 --> Size was 0
So where does the default 1MB come from?

2. New Project in eVC 4.0 with hello window code ---> Size was 0x10000 == 65536
If I hit help on the settings menu a little popup shows that default stack size is 1MB. But it has the value 0x10000 entered by default. So how does it relate?

re: Virtual Memory and Thread Stacks

B. Lee — Wed, 08 Feb 2006 09:43:18 GMT

Here is a typo fix.
I'm 'now' sure how correct(?) this may be --> 'now' should be a 'not'

re: Virtual Memory and Thread Stacks

John Eldridge — Sun, 19 Feb 2006 08:39:30 GMT

Thanks for the feedback, B. Yes, eVC4 did set the size to 64k explicitly. For VS2005, a value of zero means that the linker's default (1MB) will be used. I notified the VS team and they are looking into it.

re: Virtual Memory and Thread Stacks

RoboForm — Sun, 19 Feb 2006 12:22:42 GMT

Good!

re: Virtual Memory and Thread Stacks

Richard Plante — Wed, 01 Mar 2006 21:15:39 GMT

I'm having a program that reads a XML file using CubeWerx open source (www.cubewerx.com). Reading a small XML file (let say ~100K) works perfectly and does not generate any problem. Reading a huge XML file (currently trying 2.5Mb) is causing a stack overflow.

Reading a XML file is done recursively in CubeWerx since you have to go deep enough to the rightmost leaf to read the full content of the file. The default stack size of my program is still 1Mb and everything in CubeWerx is done from the same thread.

My question is: how come that code works correctly on a Win32 program but not on a SmartDevice program? Under Win32, my stack size is also set to the default value 1Mb and reading a 2.5Mb XML file is not generating a stack overflow.

Visual Studio and Virtual Memory

Windows Mobile Team Blog — Wed, 29 Mar 2006 19:45:13 GMT

Visual Studio reserves 1 MB of virtual memory for each of your app's threads by default.&nbsp; This is...

re: Virtual Memory and Thread Stacks

Kevin Moran — Thu, 30 Mar 2006 00:26:29 GMT

Is there any way to set this property for a c# smart device project?

Kevin

re: Virtual Memory and Thread Stacks

Mike C. — Thu, 30 Mar 2006 02:51:24 GMT

Where do you find/set this value in Visual Studio 2005?

re: Virtual Memory and Thread Stacks

kitlfirst — Thu, 30 Mar 2006 03:21:54 GMT

Mike C.,

You can find it under Project | Properties. Then you should see the dialog box. The setting is under Configuration Properties | Linker | System.

re: Virtual Memory and Thread Stacks

Mike C. — Thu, 30 Mar 2006 20:36:09 GMT

Kitlfirst,

When I go into Project | Properties in VS 2005, I get the properties tabbed window (alongside my source code tabbed windows). There is no dialog box as such.

Unfortunately, the project properties tabbed window doesn't have as many options at the VS 2003 dialog box has, as seen below:

<img src="http://itracksolutions.com/imagedump/VS2005ProjProps.gif">

process stack size and threads | keyongtech

process stack size and threads | keyongtech — Thu, 22 Jan 2009 12:36:03 GMT

PingBack from http://www.keyongtech.com/3119782-process-stack-size-and-threads