.NET Framework - Process.start() within Backgroundworker - Memory limit??

Asked By Sven

15-Jul-08 05:29 PM

Hi Newsgroup,

I am developing a C# Windows Forms application that launches processes within
a background worker..

The processes seem to have a memory limit of about 278mb. Some proccesses
that get to that
amount of used memory seem to hang ;-(

Is there a memory limit that can be adjusted ?? The physical machine has 3
GB RAM, should be enough...

Thanks
Sven

15-Jul-08 05:43 PM

I'm quite skeptical that BackgroundWorker has anything to do with it. Can
you verify that the problem doesn't occur if you start them without using
BackgroundWorker, or even if you start them manually?

--
J.

16-Jul-08 09:21 AM

Hi Jeroen,

let me 1st tell you something about the application:

- windows forms application that should act quite like a batchfile ->
launching programs out of a list,
- displays list of programs in a datagridview,
- Button_Click() - backgroundworker.RunAsync()
- backgroundworker.DoWork() - launches item per item the programs from the
list as a process.

now, I removed the bgworker.. still the same problem.

One console program consumes about 280mb within the started process and
hangs. when launching it from normal console start>execute program .... it
consumes about 400mb and exists normally.

I think the problem is the "process class" of c#. Is it possible to adjust
its maximum memorylimit, if it has a memory limit...

Any hints ?

Sven

16-Jul-08 12:56 PM

On Wed, 16 Jul 2008 06:21:02 -0700, Sven W.


As Jeroen accurately speculated.  :)


It doesn't, and your problem is unlikely to be specific to the Process
class.

If the processes being launched are hanging, you need to debug that.  That
is, debug a hung process, not the application starting the process.
Especially since the memory consumptions you're describing are so far
below any usual limitation on a modern PC, I really doubt that you've got
a memory consumption/limit problem.  There's something else going on.

Pete

02-Aug-08 05:47 AM

There is a client heap setting you can adjust for windows applications
although it applies mainly to COM+. Have a look at this article:
http://support.microsoft.com/kb/556076

--

Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
Download OWC Black Book, 2nd Edition
Exclusively on www.lulu.com/owc $15.00
Need a free copy of VSTS 2008 w/ MSDN Premium?
http://msmvps.com/blogs/alvin/Default.aspx
-------------------------------------------------------

28-Feb-09 03:59 AM

Hi Sve,

Did you ever find a solution to your problem, I am experiencing a very simialr issue.

Thanks
Jamie