Re: Virtual Memory Minimum Too Low - but no pagefile!
From: Slobodan Brcin \(eMVP\) (sbrcin_at_ptt.yu)
Date: 06/23/04
- Next message: Sean Gahan: "Re: Writting VB.net for XPe"
- Previous message: Sean Gahan: "Re: Page file"
- In reply to: Peter Boden: "Re: Virtual Memory Minimum Too Low - but no pagefile!"
- Next in thread: Kesavan: "Re: Virtual Memory Minimum Too Low - but no pagefile!"
- Reply: Kesavan: "Re: Virtual Memory Minimum Too Low - but no pagefile!"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 23 Jun 2004 18:36:22 +0200
Hi Peter,
> Hiding the "Virtual Memory is low" message box is probably only masking a
> more serious problem...
In some cases you are right.
On our systems we have 512 MB of RAM and use from 450-480 MB of ram.
"Virtual Memory is low" is triggered at 256 MB or perhaps little less I can't remember now. So I always have seen this error box,
and error box was error itself since info it provided was useless to us.
Regards,
Slobodan
"Peter Boden" <pnb2001@spambegone.yahoo.com> wrote in message news:%23vKT$6SWEHA.4032@TK2MSFTNGP11.phx.gbl...
> Hiding the "Virtual Memory is low" message box is probably only masking a
> more serious problem... I recently had a similar problem (no page file
> system), where, after some period of use, that message would be displayed.
> If ignored, we would later have some seriously odd application errors occur.
> The system tends to behave badly when most of system RAM has been exhausted.
> After a little debugging, we've found that under just the right conditions,
> our application leaks memory like a sieve...
>
> So, my recommendation is to debug what you can before hiding the warning
> message... Have you ever used Microsoft's Windbg? Great tool if you don't
> have any way to diagnose an application problem on the target itself. It
> has a "!vm" command (virtual memory) that will give you a bunch of detail on
> virtual memory usage for your entire system as well as memory usage per
> process.
>
> To debug your target with windbg, you'll have to change some of your targets
> boot parameters. Refer to this site for info on windbg and how to use it:
> http://www.microsoft.com/whdc/devtools/debugging/default.mspx
>
>
>
> "Slobodan Brcin (eMVP)" <sbrcin@ptt.yu> wrote in message
> news:%23XfOklJWEHA.3988@tk2msftngp13.phx.gbl...
> > Hi,
> >
> > Read here how to prevent this and similar info popup.
> > http://msdn.microsoft.com/embedded/community/tips/xp/popups/default.aspx
> >
> > Regards,
> > Slobodan
> >
> >
> > "MrBill" <MrBill@discussions.microsoft.com> wrote in message
> news:FB2BBE25-F299-42CD-AAB8-6523B54D2CEC@microsoft.com...
> > > I have an XP embedded image on a 512Mb CF card with the page file
> disabled and using the RAM EWF. I am at a point where when it
> > starts up, I get a "Windows - Virtual Memory Minimum Too Low" and a
> messages saying that windows will increase the size of it. If
> > there is no page file why am I getting this message?
> > > Is there something an application could be specifically requesting that
> could cause this message?
> >
> >
>
>
- Next message: Sean Gahan: "Re: Writting VB.net for XPe"
- Previous message: Sean Gahan: "Re: Page file"
- In reply to: Peter Boden: "Re: Virtual Memory Minimum Too Low - but no pagefile!"
- Next in thread: Kesavan: "Re: Virtual Memory Minimum Too Low - but no pagefile!"
- Reply: Kesavan: "Re: Virtual Memory Minimum Too Low - but no pagefile!"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|