Memory usage going crazy!!

I have a MBP with 4GB of memory and constantly see that amount being 99% used. It goes into swap all the time! I don't have too many apps running, just Mail, Safari, iTunes, and Word. Does anybody know what's happening? Thanks!

irowharderthanyou wrote:
Safari tops the list @330MB, but nothing else looks too excessive. page-in/page-out ratio is 10:1 now, but can be MUCH lower. Sometimes it's around 1:1. The current memory breakdown is:
Free: 13MB
Wired: 737MB
Active: 1.17MB
Inactive: 2.10MB
Used: 3.99GB
OK - Out of the memory shown here approximately 2.23GB is still available for use, and should be called upon by the computer when necessary. (The 2.10GB of "Inactive" RAM is RAM which was previously in use, by one of the current applications or by ones which you have now quit, but which retains its original contents in case the earlier use is required again. It is not really being "used" and is available for other apps to call on if necessary.
The Wired and Active ones are the RAM that is really currently in use.
I wouldn't be expecting a lot of "Pageout" activity in the present situation.
It may be, though , that one of the apps you commonly use isn't regularly "releasing" RAM at some times, or that it behaviour becomes nastier when using a particular "plug-in" for example. I'd keep an eye on the figures while you work for a while and check out any activity that significantly changes things.
How often do you restart your computer? (a guaranteed way of "freeing up" RAM, of course).
Cheers
Rod

Similar Messages

When i run exe built in Labview 7.1 the memory usage goes on increasing

Dear Sir/Madam
I have built an application in LabView 7.1. When i run this application and view the memory usage in Task manager, i find that the memory usage goes on increasing.
Please help.
With Regards
Ravindra Kumbhar

Hi, Ravindra,
It looks that you have memory leak in your application.
There are lot of possible reasons for memory leaks - opened in cycle and not closed references, continuosly growing arrays, memory allocation in own DLLs, etc.
Normally you should have the same behaviour in development environment as well (memory of LabVIEW.exe incresed continuously).
You should check the code, which executed repeatable (while/for loops) for allocated, but not closed resources. What you can do is following - remove (or isolate) parts of you code, executed in cycles, then check is leak present or not. So, step by step you will found the place where leak occurred.
best regards,
Andrey.

Window Memory usage even after closing windows

I've included links to a test app that does nothing but
launch a window, play a sound, close window / repeat.
When application launches it uses about 20mb of memory. When
you click on the only button, it will launch a secondary window
that will simply play a wav file. (I set the volume low but you may
want to mute it :D)
After launching and closing the window several times the
memory usage goes up considerably and *never* falls back a
significant %. (I got it to about 100MB before I decided to quit
trying to increase the memory usage. Right now it's been running
w/o any user interaction since opening about 10 windows and it's
fairly stable at around 61MB (although that appears to be
increasing w/o user interaction).
Does anyone know of any methods I can use to ensure that the
memory consumed by secondary windows does not just persist forever
even after closing the window? Is there something I'm doing wrong
here?
Example Code:
http://www.vf-server.com/air/memorytest.air
(AIR)
http://www.vf-server.com/air/memorytest.zip
(source ZIP)
Note: When I *minimize* the window it looks like garbage
collection is forced and app drops back to 11MB (on restore back to
19mb).
Edit: note in your task manager, application appears as
JBTest.exe

You can call System.gc() to force the garbage collector to
run.
Try removing the event listeners when they aren't needed
anymore. I think it is more difficult for the gc to cleanup objects
when there are host objects (like Sound) refering to JavaScript
objects and JavaScript objects refering to host objects, so you
need to be especially careful about those. It SHOULD clean them up
eventually, but it may take longer for it to figure out that those
objects are no longer in use.
You might also clear the secondaryWindow reference in the
parent document when the window closes. That reference might retard
garbage collection, too.

0.5 MB program has 832 MB memory usage even before it is run

I just uninstalled and re-installed LabVIEW 2011. I was hoping this would do something to lower the memory footprint. Alas, it did not make any difference. This is what I see:
- When I launch LabVIEW, it uses 94 MB even before I have opened a single VI, i.e. only the front end uses this much memory.
- When I open the VI (the size of the .vi file is 549 KB), memory usage goes up to 836.4 MB. This is before I have even run the program.
- Finally, when I run the program, memory usage jumps to 1.17 GB.
I find this memory usage grotesquely high. Can anyone please shed some light on what can be done? I have uploaded the VI. It's a rather simple VI.
Thanks,
Neil
Attachments:
IP QL to charge - from img.vi ‏446 KB

nbf wrote:
1) If I understand correctly, what you are saying is that when I open the VI, the data structures associated with the intensity charts and waveform graphs are initialized to default values (e.g. 0), so there is memory usage even before the program is run and anything displayed, right?
Yes, a huge array still takes a lot of memory, even though it compresses well for storage inside the VI. Once the VI is ready to run, these arrays need to be allocated in memory.
nbf wrote:
2) Is there an alternative to using the value property node that doesn't duplicate the memory content? (e.g. something like pointer or reference in C++?)
One possiblity are data value references. You can open a DVR and fill it inside the subVI, then extract slices later as needed. If done properly, you can also keep the 2D data in a shift register (yes, please learn about them!).
nbf wrote:
4) Regarding the clearing of the indicators, could you please tell me how to do that, without removing the color ramp settings?
The color ramps can be set programmatically using property nodes based on array min&max and you can assign colors for the ramp values at will.
nbf wrote:
5) You are correct that I am displaying 4000x2000 array data in an intensity graph with 400x200 pixels. But then I change the min/max of the charts/graphs to zoom into the region of interest; I can identify the region of interest only after displaying the full 4000x2000 array of data. I don't know if there is a way around this.
Do you really need to show the 2D data in three different transforms? Maybe one intensity graph is sufficient. You can apply the other transforms on the extracted slices with <<1% of the computing effort. What is the range and resolution of your data? Do you really need DBL or is a smaller representation sufficient (SGL, I16, etc). From looking at the subVI, the raw data is U16. The subVI also involves a coercion to DBL, requireing another data copy in memory. When running, make absolutely sure that the subVI front panel is closed, else additional memory is used for the huge array indicator there. For better performance, you might want to flatten the subVI to the main diagram or at least inline it.
nbf wrote:
6) Yes, I use the continuous run mode instead of a toplevel while loop. Is there a disadvantage to doing that?
As Samuel Goldwyn ("A hospital is no place to be sick") might have said: "Run continuously is no way to run a VI"
Run continuously is a debugging tool and has no place in typical use. What it basically does is restart the VI automatically whenever it completes, and as fast as the CPU allows. It is mostly useful to quickly test subVIs that don't have a toplevel loop and play with inputs to verify results. Any toplevel VI needs a while loop surrounding the core code. Period!
So, my suggested plan of action would be:
Use a while loop around your toplevel code
Decide on the minimal representation needed to faithfully show the data.
Keep a single copy of the 2D array in a DVR
You optionally might want to undersample the data for display according to the pixel resolution and use other means of zooming and panning. For zooming, you could extract a differently sampled small array subset and adjust x0 and dx of the axes accordingly.
Use a single 2D graph (if you need to see the various transforms, add a ring selector and transform the 2D array in place. Never show more than one intensity graph.
See how far you get.
LabVIEW Champion . Do more with less code and in less time .

JMS C API -- Memory usage

Hi
Im writing an application to using JMS C API on Soalris platform.
When Im executing the program , after the connection is made memory usage is shooting up !!!
Do JMS library reserve any memory when a connection is made. ???
Does JMS api create any threads ???
Adv Thanks
Chandu
Edited by: Raja_cs on May 27, 2008 11:40 PM

The client runtime is caching messages sent by the broker (default number is 1000). So I'd expect to see memory usage going up.

Premiere crashes when exceeding ~1.2GB memory usage

This is extremely annoying. I have found Premiere to crash when it hits around 1.2GB to 1.5GB of memory usage on medialayer.dll or something. I was able to crash Premiere in just a matter of seconds after launching it and opening my project. I work quickly, so this happens frequently.
Q9450 Yorkfield Quadcore (12MB Cache), clocked at 3.2GHz
4GB of 1200 RAM
All my scratch disks are set to my second partition, which has around or at least 200GB of free space. My page file is set to about 4GB. My machine is defragmented daily by Diskeeper Pro 2008.
I am dealing with 26 video files and have frame thumbnails displaying in the timeline thing (it makes everything all the more easier for what I am specifically doing) and adds up to around a total of 9 to 10 hours of video and audio. I'm chopping out the intro, credits, and midtro from each video, which is basically what I am doing.
However, I am currently downloading the latest update (which is like 50.3MB) that might possibly fix this issue. At least I hope it does. :( This crash/memory leak is going to drive me insane if it cannot be fixed.
EDIT :: I have observed that every time I save, the memory usage goes up by 200KB to 500KB. For each frame thumbnail that Premiere loads, the memory usage goes up by a whopping 2MB+. This will and does quickly add up for the work I'm doing. Photoshop never unloads any of this memory!
EDIT2 :: By the way, the frame thumbnails are 88x65 sized thumbnails.
EDIT3 :: Even with the latest version and update, Premiere Pro CS3 still crashes for the same reason. I haven't seen the memory usage at 1GB though.
EDIT4 :: Latest updates help though, but does not fix the problem. When I minimize Premiere, usage is 17 MB. When I bring it back up, usage is 32MB. I can keep resetting the usage to 17/32MB simply by just minimizing Premiere and bringing it back up again (and the memory usage reset is about instant). So far I've reset it numerous times when reaching levels of around 600MB to 800MB of memory usage and haven't crashed in my current session due to the memory leak yet.
This seems to be only a temporary solution.
http://www.hlrse.net/Qwerty/premiere-memoryleak-workspace.gif
That is my current workspace. I literally keep task manager open with Premiere highlighted like that so that I can watch the memory usage levels (to know when to 'reset' the memory usage) as I work. Right now all I'm doing is zooming in and out, and splitting videos in two (or multiple pieces).

Q9450 Yorkfield (12MB Cache) @ 3.2GHz
2GB G.Skill PC2-6400 (400MHz) x2 (4GB total, running with 3.5GB due to 32-bit limitations)
NVIDIA FX5200 (temporary, waiting for ATI HD4850 to come back from RMA)
500GB Seagate Barracuda 7200.1 SATA-II w/ SATA-II enabled
I have my 500GB harddrive partitioned into two partitions: 40GB (C) and 425GB (D). C is for Windows XP (includes drivers, codecs, and things that relate heavily to the core of Windows; stuff that isn't important enough to backup). D is for everything else, which includes games, utilities/tools, media (images, video, music), developer material, etc.
On D, you would find the following logical layout of folders:
Developer, Games, Media, Network, Utilities, Mozilla Firefox, Temp.
Temp is so that I can (in an organized fashion) set the temporary locations and scratch disks for programs here. All scratch disks are set to D:\Temp\Premiere, and currently reports 121.9GB of free space. I can easily free up 114GB to 240GB of material on D though (which I plan to do sometime anyway).
What information do you want to know? Be specific, I'm not stupid and illiterate like most people.
EDIT :: I didn't mention this in my post, but I did take the precautions to search through the Troubleshooting database for Premiere, and I did read through the optimizations for Windows XP article (which I already had the same suggestions applied to my computer since the dawn of time -- so that wasn't really useful).
EDIT2 :: I checked the troubleshooting link and none of those really apply. (Do you even know what a memory leak is?)
=P

Max Memory Usage

I am wondering if it is normal for a Mac to have only 40 to 50% memory usage no matter how many apps are running.
I have a G4 Aluminum PB with 15.2" monitor. I upgraded the memory to 2GB, and according to the Activity Monitor, the memory usage is normally about 40%, and it rarely goes over 50%. I try running Word, Excel, iMovie, Photoshop, FinalCut, etc all at the same time. As I run more applications, the memory usage inches up little at a time, but the memory usage goes up to only 50%.
I am just curious. Is this normal? I spent good amount of money for those memory modules, and I want them to be working at 100%.
FYI, the original memory module (512MB) did go up to nearly 100% from time to time. That is why I upgarded.

With a Photoshop CS2 and Adobe Bridge open, i have like 15megs "free". 300 megs is inactive.
I have a what I consider a hight ratio of pages in/pages out. It is at 71,135/17606. Is that normal when working with one 3 to 4 meg file? I was working with some very large files (300megs) a couple weeks ago, and things seem to be running slower ever since. My thought is maybe there is some cache files sitting around that it's it holding onto, but I don't know where I would find them or how to delete them.
Thanx for your help.

Pix high memory usage

the memory of my PIX 525 is up and up, i need freed memory, How do i meke this??
TKS

A few questions before I give the easy answer:
Do you use the PIX for point-to-point VPN between sites?
Do you use the PIX as a VPN concentrator for end users?
Do you have a DMZ or multiple DMZs?
Has anything recently changed in your network that would have increased traffic through your PIX?
I mention these things because they all require CPU resources and memory.
The easiest way to free up memory is to reboot the PIX. Of course, this is not always an option but the results are very predictable. If after the reboot the memory usage goes right back up to previous levels then it's time to do a traffic study of your network and determine if this PIX has the horsepower you require or if some other network re-design is in order.
Hope this helps.

N70 memory going crazy!!Help!!

My N70, after nearly 2 yrs of usage, is suddenly going crazy. The phone memory is getting filled up on its own accord and now shows 0KB to be free. I cannot open any of the application even to delete them.
The memory card (1GB) has a good 207MB free.
I read the posts about resetting my phone using *#7370#.. but I am a bit apprehensive about this. Currently I am backing up my phone as well as memory card.
Can somebody guide please?
Thanks

hi there kgauri
The best solutions it's REALLY do *#7370#.
this will erase all the phone data and setting the phone factory settings.
it will work just fine!oh...DO NOT do a memory backup to the MMC and then restore it...if the problem it's in any aplication...the problem will reapear..
Do a set by step backup..put your sms on the MMC..copy the contacts and any aplcation to your MMC.
Cheers
My other phone it's a Nokia!!

Am running Firefox 7.0.1 now. Normal memory usage is 157mb but when running Facebook (not running apps nor games), it goes up to 553mb Why?

Am running Firefox 7.0.1 now. Normal memory usage is 157mb but when running Facebook (not running apps nor games), it goes up to 553mb Why?

I encountered the same type of problem. Firefox running terribly slowly and slowing down my entire machine (Core i5 with 256GB SSD). Searching the forums, I found a couple of things about troubleshooting performance issues, one of which was to use '''hardware acceleration''', that is on by default. It was turned on on my PC, '''so I tried deactivating it, and it worked!'''
So doing the exact opposite as Mozilla support said solved the problem. It is really a pain now to work with Firefox. I'm using it because I have no choice, but I'd recommend IE and Chrome over Firefox... Whatever, the market will decide once Firefox has become to crappy...

Very high memory usage..possible memory leak? Solaris 10 8/07 x64

Hi,
I noticed yesterday that my machine was becoming increasingly slow, where once it was pretty snappy. It's a Compaq SR5250NX with 1GB of RAM. Upon checking vmstat, I noticed that the "Free" column was ~191MB. Now, the only applications I had open were FireFox 2.0.11, GAIM, and StarOffice. I closed all of them, and the number reported in the "Free" column became approximately 195MB. "Pagefile" was about 5.5x that size. There were no other applications running and it's a single user machine, so I was the only one logged in. System uptime: 9 days.
I logged out, logged back in, to see if that had an affect. It did not. Rebooted and obviously, that fixed it. Now with only FireFox, GAIM, and a terminal open, vmstat reports "Free" as ~450MB. I've noticed if I run vmstat every few seconds, the "Free" total keeps going down. Example:
unknown% vmstat
kthr      memory            page            disk          faults      cpu
r b w   swap free re mf pi po fr de sr cd s0 s1 s2   in   sy   cs us sy id
0 0 0 870888 450220 9 27 10 0 1 0 8 2 -0 -0 -0 595 1193 569 72 1 28
unknown% vmstat
kthr      memory            page            disk          faults      cpu
r b w   swap free re mf pi po fr de sr cd s0 s1 s2   in   sy   cs us sy id
0 0 0 870880 450204 9 27 10 0 1 0 8 2 -0 -0 -0 596 1193 569 72 1 28
unknown% vmstat
kthr      memory            page            disk          faults      cpu
r b w   swap free re mf pi po fr de sr cd s0 s1 s2   in   sy   cs us sy id
0 0 0 870828 450092 9 27 10 0 1 0 8 2 -0 -0 -0 596 1193 570 71 1 28
unknown%Output of prstat -u Kendall (my username ) is as follows:
   PID USERNAME SIZE   RSS STATE PRI NICE      TIME CPU PROCESS/NLWP
2026 Kendall   124M   70M sleep   59    0   0:01:47 1.4% firefox-bin/7
1093 Kendall    85M   77M sleep   59    0   0:07:15 1.1% Xsun/1
1802 Kendall    60M   15M sleep   59    0   0:00:08 0.1% gnome-terminal/2
1301 Kendall    93M   23M sleep   49    0   0:00:30 0.1% java/14
1259 Kendall    53M   15M sleep   49    0   0:00:32 0.1% gaim/1
2133 Kendall 3312K 2740K cpu1    59    0   0:00:00 0.0% prstat/1
1276 Kendall    51M   12M sleep   59    0   0:00:11 0.0% gnome-netstatus/1
1247 Kendall    46M   10M sleep   59    0   0:00:06 0.0% metacity/1
1274 Kendall    51M   13M sleep   59    0   0:00:05 0.0% wnck-applet/1
1249 Kendall    56M   17M sleep   59    0   0:00:07 0.0% gnome-panel/1
1278 Kendall    48M 9240K sleep   59    0   0:00:05 0.0% mixer_applet2/1
1245 Kendall 9092K 3844K sleep   59    0   0:00:00 0.0% gnome-smproxy/1
1227 Kendall 8244K 4444K sleep   59    0   0:00:01 0.0% xscreensaver/1
1201 Kendall 4252K 1664K sleep   59    0   0:00:00 0.0% sdt_shell/1
1217 Kendall    55M   16M sleep   59    0   0:00:00 0.0% gnome-session/1
   779 Kendall    47M 2208K sleep   59    0   0:00:00 0.0% gnome-volcheck/1
   746 Kendall 5660K 3660K sleep   59    0   0:00:00 0.0% bonobo-activati/1
1270 Kendall    49M   10M sleep   49    0   0:00:00 0.0% clock-applet/1
1280 Kendall    47M 8904K sleep   59    0   0:00:00 0.0% notification-ar/1
1199 Kendall 2928K 884K sleep   59    0   0:00:00 0.0% dsdm/1
1262 Kendall    47M 2268K sleep   59    0   0:00:00 0.0% gnome-volcheck/1
Total: 37 processes, 62 lwps, load averages: 0.11, 0.98, 1.63System uptime is 9 hours, 48 minutes. I'm just wondering why the memory usage seems so high to do...nothing. It's obviously a real problem as the machine turned very slow when vmstat was showing 195MB free.
Any tips, tricks, advice, on which way to go with this?
Thanks!

Apologies for the delayed reply. School has been keeping me nice and busy.
Anyway, here is the output of prstat -Z:
   PID USERNAME SIZE   RSS STATE PRI NICE      TIME CPU PROCESS/NLWP
2040 Kendall      144M   76M sleep   59    0   0:04:26 2.0% firefox-bin/10
28809 Kendall     201M 193M sleep   59    0   0:42:30 1.9% Xsun/1
2083 Kendall      186M   89M sleep   49    0   0:02:31 1.2% java/58
2260 Kendall       59M   14M sleep   59    0   0:00:00 1.0% gnome-terminal/2
2050 Kendall       63M   21M sleep   49    0   0:01:35 0.6% realplay.bin/4
2265 Kendall     3344K 2780K cpu1    59    0   0:00:00 0.2% prstat/1
29513 Kendall     71M   33M sleep   39    0   0:07:25 0.2% gaim/1
28967 Kendall     56M   18M sleep   59    0   0:00:24 0.1% gnome-panel/1
29060 Kendall     93M   24M sleep   49    0   0:02:58 0.1% java/14
28994 Kendall     51M   13M sleep   59    0   0:00:23 0.1% wnck-applet/1
28965 Kendall     49M   14M sleep   59    0   0:00:33 0.0% metacity/1
   649 noaccess   164M   46M sleep   59    0   0:09:54 0.0% java/23
28996 Kendall     51M   12M sleep   59    0   0:00:50 0.0% gnome-netstatus/1
2264 Kendall    1352K 972K sleep   59    0   0:00:00 0.0% csh/1
28963 Kendall 9100K 3792K sleep   59    0   0:00:03 0.0% gnome-smproxy/1
ZONEID    NPROC SWAP   RSS MEMORY      TIME CPU ZONE
     0           80          655M 738M    73%       1:18:40 7.7% global
Total: 80 processes, 322 lwps, load averages: 0.27, 0.27, 0.22Sorry about the bad formatting, it's copied from the terminal.
In any event, we can see that FireFox is sucking up 145MB (??!?!!? crazy...) XSun, 200MB, and java 190MB. I'm running Java Desktop System (Release 3) so I assume that is what accounts for the the high memory usage RE: java process. But, XSun, 200MB?
Is this normal and I just need to toss another gig in, or what?
Thanks

Indesign CC freezes and maxes out memory usage in Windows 7

I'm having a problem where Indesign will freeze and when I check on it in Task Manager I can see the memory usage climbing until it's using all free memory. I have to kill the task to get it to stop. I have 8GB and it maxed out at 6.5gb this morning. I'm on Windows 7 Pro and am using the 64-bit version of Indesign with the most recent update.

The document I'm working on now is only about 35 pages with 1-3 images per page, nothing too crazy. I don't have any extra plugins from what I recall - how do I check?
I'm using Photoshop and sometimes Illustrator at the same time, but have plenty of free memory until ID goes nuts.

Problem with scanning and memory usage

I'm running PS CS3 on Vista Home Premium, 1.86Ghz Intel core 2 processor, and 4GB RAM.
I realise Vista only sees 3.3GB of this RAM, and I know Vista uses about 1GB all the time.
Question:
While running PS, and only PS, with no files open, I have 2GB of RAM, why will PS not let me scan a file that it says will take up 300Mb?
200Mb is about the limit that it will let me scan, but even then, the actual end product ends up being less than 100Mb. (around 70mb in most cases)I'm using a Dell AIO A920, latest drivers etc, and PS is set to use all avaliable RAM.
Not only will it not let me scan, once a file I've opened has used up "x" amount of RAM, even if I then close that file, "x" amount of RAM will STILL be unavaliable. This means if I scan something, I have to save it, close PS, then open it again before I can scan anything else.
Surely this isn't normal. Or am I being stupid and missing something obvious?
I've also monitored the memory usage during scanning using task manager and various other things, it hardly goes up at all, then shoots up to 70-80% once the 70ishMb file is loaded. Something is up because if that were true, I'd actually only have 1Gb of RAM, and running Vista would be nearly impossible.
It's not a Vista thing either as I had this problem when I had XP. In fact it was worse then, I could hardly scan anything, had to be very low resolution.
Thanks in advance for any help

55%, it's still 1.6Gb....there shouldn't be a problem scanning something that it says will take up 300Mb, then actually only takes up 70Mb.
And not wrong, it obviously isn't releasing the memory when other applications need it because it doesn't, I have to close PS before it will release it. Yes, it probably is supposed to release it, but it isn't.
Thank you for your answer (even if it did appear to me to be a bit rude/shouty, perhaps something more polite than "Wrong!" next time) but I'm sitting at my computer, and I can see what is using how much memory and when, you can't.

High memory usage when many tabs are open (and closed)

When I open Firefox the memory usage is about 70-100 MB RAM. When I'm working with Firefox I often open 15-20 tabs at once, then I close them and open others. Memory usage increaes up to 450 - 500 MB RAM. After closing the tabs the usage usually decreases, but after sometime. It starts decreasing very slow and never comes back to the level from the beginning. After few hours of work Firefox uses about 400 MB RAM even if one tab is open. First I thought it's because of my plugins (Firebug, Speed Dial, Adlock Plus) but I've checked it and it's not. I reinstalled Firefox but the problem occurs as well. I'm not sure if it's normal. Could you help me, please?

Hi,
Not an exact answer but please [http://kb.mozillazine.org/Reducing_memory_usage_(Firefox) see this.] The KB article ponders through various general situations which may or may not be applicable to specific instances but nevertheless could be helpful.
Useful links:
[https://support.mozilla.com/en-US/kb/Options%20window All about Tools > Options]
[http://kb.mozillazine.org/About:config Going beyond Tools > Options - about:config]
[http://kb.mozillazine.org/About:config_entries about:config Entries]
[https://addons.mozilla.org/en-US/firefox/addon/whats-that-preference/ What's That Preference? add-on] - Quickly decode about:config entries - After installation, go inside about:config, right-click any preference, enable (tick) MozillaZine Results to Panel and again right-click a pref and choose MozillaZine Reference to begin with.
[https://support.mozilla.com/en-US/kb/Keyboard%20shortcuts Keyboard Shortcuts]
[http://kb.mozillazine.org/Profile_folder_-_Firefox Firefox Profile Folder & Files]
[https://support.mozilla.com/en-US/kb/Safe%20Mode Safe Mode]
[http://kb.mozillazine.org/Problematic_extensions Problematic Extensions/Add-ons]
[https://support.mozilla.com/en-US/kb/Troubleshooting%20extensions%20and%20themes Troubleshooting Extensions and Themes]

Having a problem with Excessive "modified" memory usage in Win7 x64, upwards of 3.6GB, any suggestions?

I have 6GB of ram, a fresh install of Windows 7 x64, and the screenshot shows what happens after leaving my PC on for a couple days. (3782+MB being used by modified memory ATM).
http://wow.deconstruct.me/images/ExcessiveMemory.jpg
Any ideas on this?
Edit:
Added this after first round of suggestions
http://wow.deconstruct.me/images/NotSoExcessiveMemory.jpg
This is uptime of around 2 hours.
The first image is of uptime of around 3-5 days.

Matthew,
The only reason why these pages are kept on the modified list indefinitely is because the system doesn't have any available pagefile space left. If you increase the size of the pagefile the system will write most of these pages to disk and then move them from the modified list to the standby list. Standby pages are considered part of "available memory", because they can be reused for some other purpose if necessary.
Whether this would "fix" the problem or not depends on what the actual problem is. If it's an unbound memory leak then increasing the size of the pagefile will simply allow the system to run longer before it eventually hits the maximum pagefile size limit, or runs out of disk space. On the other hand, if it's a case of some application allocating a lot of memory and not using it for a long time, then increasing the pagefile might be a perfectly valid solution.
Allowing the system to manage the size of the pagefile actually works well in most cases. Pagefile fragmentation (at the filesystem level) can only occur when the initially chosen size is not large enough and the system has to extend it at run time. For win7 we have telemetry data that shows that even for systems with 1 GB of RAM, less than 0.1% of all boot sessions end up having to extend the pagefile, and this number is even lower for larger amounts of RAM. If you think you are in that 0.1% and your pagefile might be getting fragmented, you can manually increase its minimum size such that the total system commit charge stays below 80% even if you run all your apps at once (80% is the threshold at which the pagefile is automatically extended). This will make sure the pagefile is created once and then stays at the same size forever, so it can't fragment. The maximum size can either be set to the same value as the minimum, or you can make it larger so that the system is more resilient to memory leaks or unexpectedly high loads.
By the way, Windows doesn't use pagefiles as "extra memory", it uses them as a backing store for private pages, just like regular files are used as a backing store for EXEs/DLLs and memory mapped files. So if the system really has more than enough RAM (like in your second screenshot, where you have 3.6 GB of free pages) you shouldn't see any reads from the pagefile. You can verify this by going to the Disk tab in the resource monitor and looking for any disk IO from pagefile.sys. On smaller systems that don't have an excess of free pages you may see periodic reads from the pagefile, and this is expected because the total amount of data referenced by the OS/drivers/processes is larger than the total RAM. Forcefully keeping all pagefile-backed pages in memory (which is what disabling the pagefile does) would simply mean some other pages (memory mapped files, DLL code or data etc) would have to be paged out.
Regarding further troubleshooting steps: If the system runs fine with a larger pagefile (commit charge stabilizes well below 80%, and you no longer see gigabytes of modified pages accumulating in memory) then you don't really need to do anything. If the problem persists, you can check for any processes with an abnormally high commit charge, and also check kernel memory usage in task manager. If it's a kernel leak you can usually narrow it down to a particular driver using poolmon.exe or kernel debugger.

Memory usage going crazy!!

Similar Messages

Maybe you are looking for