New
#1
Is it only Mozilla Developer Preview? Or caused by other programs? If the former then it should likely be directed to the Mozilla mailing list or forum that deals with experimental releases of Mozilla software.
If the latter please give more information. For instance the Resource Monitor screen shot showing memory usage.
Hello SAEED,
By chance, did you disable your page file, set your page file to be too small, or are you low on hard drive space?
Virtual Memory Paging File - Change
If no other application causes a problem, chances are this developmental program has a huge memory leak.
tax MilesAhead
This is a screenshot of the page when error occurs
hi Brink and tankyou for answer me
I had to disable page file , because I thought it unnecessary with 4GB RAM.
Anyway enable it again.
I hope the problem is resolved
With the pagefile disabled the commit limit will be something less than RAM size. This can cause some serious problems, even when there is a great deal of available or even free memory available. It can also substantially reduce the amount of memory available. I would urge you to re-enable the pagefile to System Managed.
I have always hated that error dialog because it is so vague in meaning. "Low on memory" has multiple meanings and it doesn't tell you which one. A lack of RAM will reduce performance, possible seriously, but will rarely cause other problems. Hitting the commit limit will cause serious problems. But from the Task Manager numbers it is clear neither condition is true.
Out of memory errors are typically caused when the condition of a processes private address space causes a memory allocation to fail. But closing any number of other applications will have no effect on this situation.
SAEED,
If you set your page file to be managed by the system and restarted the PC afterwards, then you should be good to go if that was the only issue. :)
Enabling paging may do it. I had a system with 2 GB ram that really did not need to page. But the system expected it. I set Superfetch to the default settings (3 and 3) and enabled the paging. All the out of memory errors went away.
Enabling the pagefile may not solve the current problem but is good insurance against future problems. The big problem in doing this is the drastic reduction in the commit limit. With 4 GB RAM and a system managed pagefile this will initially be almost 8 GB. But that is only a soft limit and could go as high as near 16 GB in an emergency without any change in configuration. That should be enough for any normal workload with a comfortable safety margin besides.
With no pagefile the commit limit is somewhat less than RAM size, in this case 4026 MB. And this is a hard limit with no possibility of increasing it. Bad things happen when the commit limit is reached. If you are lucky it may mean only an error message. Or it could mean an application failure with the loss of any unsaved work. Or it could mean a BSOD with an ubrupt termination of all processes.
The commit charge and limit is difficult to explain and I will not try to do so here. It has nothing to do with actual usage of RAM, the pagefile, or any combination of the two. Just be sure the commit charge never reaches the limit.
Advice to disable the pagefile (which can be found all over the Internet) is almost always misguided and is based on a misunderstanding of how the pagefile is actually used. The pagefile is not just an alternative to RAM when it runs short. It was designed to improve performance and it usually does.
I don't know about SP1 but pre-SP1 W7 Ultimate there's some kind of bug. I would have over a GB on standby and be running no memory intensive programs. I'd still get the occasional OOM. It likes prefetch settings to be the default and it likes a page file. Even though the page file is virtually unused. So as compromise I set a 4 GB page file. No more OOM. Of course the min/max both set to 4 GB does not work for everyone. But it works for me.