Page fault handler will be paged out

Hi All,
I have a doubt. I know PageFault Handler handles the page fault error. Will PageFault thread be preempted?
Also I wanted to know whether PageFault handler when it is Preempteed will be Paged out?

page faults happen on the thread where the fault occurs. the IRQL will raise to dispatch to handle the exception, but the wait for the page will be synchronous. no, the handler will not page out
d -- This posting is provided "AS IS" with no warranties, and confers no rights.

Similar Messages

On iPhoto, I can no longer access the 'Classic' option which would lay out my photos on the page. It will send them as attachments only. I need the page layout for my work. Any thoughts as to why this has changed?

On iPhoto, I can no longer access the 'Classic' option which would lay out my photos on the page. It will send them as attachments only. I need the page layout for my work. Any thoughts as to why this has changed? It used to fully lay out the photos so I could add notes and detailed information before I sent them. I am thinking it is something simple that I have just missed...

The "Photos" view has been replaced by the Media Browser.
Most applications will show you the Photos icon in the Sidebar, when you need to select photos in a file chooser dialoge. Mail, Safari, the iWork apps. See Terence Devlin's User Tip: How to Access Files in iPhoto
For example, in the File > Open dialogue in Preview I am seeing this in the sidebar.

OS Windows Vista Ultimate - HP LAser Jet 1000 - Firefox will not print out internet page etc...

OS Windows Vista Ultimate - HP Laser Jet 1000 - Firefox will not print out internet page etc...
That simple, find an page you want to print, hit the print button and zero zip zlich.
Works just fine with IE?????

See this: <br />
http://kb.mozillazine.org/Problems_printing_web_pages

My iPhone 4S can't support camera 360 apps.Once I open the apps 3 sec it will auto jump out to the home page.Look likes the apps crashed.Isn't my iPhone problem or the apps got bug?Please help me.TQ

My iPhone 4S can't support camera 360 apps.Once I open the apps 3 sec it will auto jump out to the home page.Look likes the apps crashed.Isn't my iPhone problem or the apps got bug?Please help me.TQ

Close all open apps by double-tapping the home button, then swiping up and off the screen with the app window (not the smaller icon).
Reset your device: hold down the home button along with the sleep/wake button until the screen goes black and you see the Apple, then let go. (No data loss)

Since downloading Yosemite, Safari will close itself out at times and I loose all the pages I had open. How can I stop this from happening?

Since downloading Yosemite, Safari will close itself out, when I reopen it all of my pages are gone. How do I stop this from happening?

But if iit won't stay open, then it's quitting unexpectedly which is the same as a crash.
There has to be a reason for that which a crash report should reveal.
Check ~/Library > Logs > Diagnostic Reports

How to fix: Unhandled page fault on read access to 0x00000000 at address 0x00aa4088 .

hi
i recently downloaded a game (assassins creed I), i opened it and the intro showed up after that the screen went white, then black and a window came up calld exception raised and then below it, it said, Unhandled page fault on read access to 0x00000000 at address 0x00aa4088.
i have tried opening it many times and the same results come up.
i've looked everywere and found that other people have had this same problem but no one has fixed it yet
any help will be appreciated
thanks

I did try the OP's solution, but it proved to be only temporary. Take a gander at my proposition, and if you are experiencing many issues with your MBA and WiFi Connection, try doing all of the possible fixes located on these forums to see which one (hopefully) works for you. Here's my attempt at a solution.
Well, after toying around with many of the settings on the MBA, I then began to work on the AirPort Extreme (Gigabit Version) and I discovered that the MBA would only connect when I selected "Interference Robustness" when configuring the MBA. This made a difference no matter what "Wireless Mode" the AE was in, be it 802.11n(b/g) Support, plain 802.11n(5Ghz), ect. So, try that out if you have an AirPort Extreme/Express and MBA, and post your results. The MBA is running 10.5.5 with only one update remaining (10.5.6).
{This has posted in various threads by me, myself, and I, and I am only reposting so that many threads are aware of this. Hope it helps at least one person.}

LabVIEW 4.0 Invalid Page Fault Errors

I've got myself stumped on this problem - we had a LabVIEW based PC/DAQ system that started giving invalid page fault errors and crashing in Win95. This may have been concident with a revision to a vi file. To rectify the problem I've tried the following:
1. Reinstall LabVIEW 4.0 with NI-DAQ 6.6
2. Wipe HD, reinstall Win95, LV 40, NIDAQ 6.6
3. Full HD scan and MEMTEST86 memory test
4. Install on another PC
The PCs are P5-60 Gateways with 128 MB of RAM. DAQ config is 1 AT-AO-10 and 1 AT-MIO-16DE-10
Nothing seems to help. With a reinstall of LV40, I can get it to run, but once I copy the .vi files back into User.lib LV crashes.
Does LV40 look in User.lib upon startup and crash if it finds something it doesn't like? A corrupted vi?
Thanks!

Blair Hogg wrote:
...guess the next step is to go in and load each .vi manually to see if there is one that is causing problems. Hopefully some of you out there are finding this somewhat interesting, and I'm not just cluttering up the forum...
Hi Blair Hogg,
I like your sence of humor ;-) Don't worry, even if nobody reads your
thread (well... I just did) you need to write MUCH more for it to be
considered clutter. Now, if you had created 25 duplicates of the same
thread, then we would be talking about cluttering...
I'm curious about this issue even thought NI only supports LabVIEW two
versions back - officially. My guess is that a VI is corrupted and
kills LabVIEW when the VI loads. Therefore I do aggree that the
procedure from now on is to load every single VI one by one and then
notice what VI will make LabVIEW crash. I might be able to repair that
VI if you submit it to the thread.
Another thing to try is to mass compile the user.lib. The log after the
mass compile will show if any VIs were bad or had problems getting
compiled.
Well, I hope you find the source for this issue - even if I'm the only one that cares ;-)
Have Fun!
- Philip Courtois, Thinkbot Solutions

Fault handling in DIServer Interact

Good Day Mentors,
I'm currently testing out how the DIServer works.
Now, I am testing Fault handling with the DI Server,
and would want to know if there is a way to get multiple Errors from an DI Server Interact call.
My test scenario was adding 2 Sales Orders into SAP via DI Server using the Interact Call(Not BatchInteract).
The actual SOAP call sent , with comments, is as below:
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
<env:Header>
<SessionID>5659CCC6-2E15-4664-BFA2-4E6A3BDD3E35</SessionID>
</env:Header>
<env:Body>
<dis:Add xmlns:dis="http://www.sap.com/SBO/DIS">
<Service>OrdersService</Service>
<Document>
<DocType>dDocument_Items</DocType>
<DocDate>2014-05-09</DocDate>
<DocDueDate>2014-05-10</DocDueDate>
<CardCode>C23900</CardCode>
<Comments>DI Server Test - ADD</Comments>
<DocumentLines>
<DocumentLine>
<ItemCode>A00003</ItemCode>
<Quantity>2</Quantity>
</DocumentLine>
<DocumentLine>
<ItemCode>TESTITTEM02</ItemCode> 
<Quantity>2</Quantity>
</DocumentLine>
</DocumentLines>
</Document>
</dis:Add>
<dis:Add xmlns:dis="http://www.sap.com/SBO/DIS">
<Service>OrdersService</Service>
<Document>
<DocType>dDocument_Service</DocType>
<DocDate>2014-05-09</DocDate>
<DocDueDate>2014-05-10</DocDueDate>
<CardCode>C20000</CardCode>
<Comments>DI Server Test - ADD</Comments>
<DocumentLines>
<DocumentLine>
<ItemDescription>Printer Servicing</ItemDescription>
<AccountCode>499999</AccountCode> 
</DocumentLine>
</DocumentLines>
</Document>
</dis:Add>
</env:Body>
</env:Envelope>
I commented the parts that should throw errors, which are the non existent ItemCode and AccountCode in 2 separate Sales Orders.
I was hoping to get a Fault Response from the DIServer which tells me that there are two error from 2 different Documents.
Basically, 2 separate error messages for the 1st Sales order(non existent Item Code) and 2nd Sales Order (Non Existent Account Code).
But the Fault Response I got from the DIServer was this:
<?xml version="1.0" ?>
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
<env:Body>
<env:Fault>
<env:Code>
<env:Value>env:Receiver</env:Value>
<env:Subcode>
<env:Value>-1</env:Value>
</env:Subcode>
</env:Code>
<env:Reason>
<env:Text xml:lang="en">Error in SOAP command 'Add'</env:Text>
</env:Reason>
<env:Detail>
<Command>Add</Command>
<SessionID>5659CCC6-2E15-4664-BFA2-4E6A3BDD3E35</SessionID>
</env:Detail>
</env:Fault>
</env:Body>
</env:Envelope>
The fault response only tells me that there is an error, but nothing specific to the documents. Just something specific to the actual SOAP call.
If I something is not clear, please do clarify with me.
I'm using SAP B1 9.0 PL05.
Thanks in advance!
Sean

Hi Sean,
I don't think there is such a feature available. This is standard behaviour in SBO - same for UI and DI API. The first problem/error found will abort the action and message is shown and in this case it is one action ( interact).
regards,
Maik

Fault handling in osb using publish

Hi all,
i am new to OSB, every thing is working fine. i will explain how we design the basically we have inbound and outbound. call inbound as 'aaaa' and outbound as "bbbb". we have created the proxy and BS which will communicate with EBS, BAM and B2B. i have created BS for all the three. from PS i used 2 assign and 1 publish activity. we are publishing directly to BS correspondingly. since i am not using any route activity i could not get the error back or any invocation error messages. can any one tell how to capture the error and place it into BAM report. we can transform data to BAM we just need to get the details about the fault handling in OSB.
thanks ----

Hi prabu,
thanks for your response.
As we have the discussion on this issue for quit a long time. i have configure the error handler in the proxy services when my EBS throws the error. error handler come active and some data is published to bam. here i got the problem is that, the PO which we are sending is one way or fire and forget when using Publish action. when the PO hit the EBS, i.e. when error message is passed through the test XML, error is occuring and and reporting to bam with some null values. i need to capture the data processed at that transaction. is it possible to capture the data in error handler which is errored out in message flow of PS.
can you please help me
thanks--
anil

11g: Help regarding fault handling framework

I am trying to implement a POC demonstrating the fault handling framework using fault policies. I am trying to handle remote and business faults. These faults are being thrown explicitly in the code. But I dont see the framework coming into picture. Here are the fault policies and fault bindings files
The POC does the following
1. If input is R, throws a remote fault.
2. If input is B1, throws a business fault. There is a catch defined for this. But as we also have a policy for this error, we expect the policy overrides the catch
3. If input is B2, throws a business fault. There is no catch defined for this. We expect the policy to handle this.
4. If any other input, we return a string.
<?xml version="1.0" encoding="UTF-8"?>
<faultPolicies xmlns="http://schemas.oracle.com/bpel/faultpolicy"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<faultPolicy version="2.0.1" id="ComponentFaults"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.oracle.com/bpel/faultpolicy"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Conditions>
<faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
name="bpelx:remoteFault">
<condition>
<action ref="ora-human-intervention"/>
</condition>
</faultName>
<faultName xmlns:ns1="NS_B1"
name="ns1:LP_B1">
<condition>
<action ref="ora-human-intervention"/>
</condition>
</faultName>
<faultName xmlns:ns2="NS_B2"
name="ns2:LP_B2">
<condition>
<action ref="ora-human-intervention"/>
</condition>
</faultName>
</Conditions>
<Actions>
<Action id="ora-human-intervention">
<humanIntervention/>
</Action>
</Actions>
</faultPolicy>
</faultPolicies>
Here is the fault-bindings.xml file
<?xml version="1.0" encoding="UTF-8"?>
<faultPolicyBindings version="2.0.1"
xmlns="http://schemas.oracle.com/bpel/faultpolicy"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<component faultPolicy="ComponentFaults">
<name>BPEL</name>
</component>
</faultPolicyBindings>

I created another bpel in the same composite that calls the original bpel. So now, those errros are supposed to travel to calling bpel.
Fault policies are coming into effect now. So, one part of the problem is solved, that atleast syntax and all is correct, and the fwk does work (!) but another one has opened - why is the fault not getting handled by the fwk if there is a single bpel that is throwing and not catching those faults.
Also, even in this new avatar, fault b1 is getting handled by the catch in BPEL process, while the fault policies are supposed to override any catches in bpel code.
What I was attempting was, throwing the fault in a bpel process and expecting the fault handling fwk to handle it.
It turns out, the framework is not capable of doing this, its only capable of handling faults coming after an invoke activity.
Consulted Oracle Support on this. Their response
The behavior within the single composite you are seeing is correct and is by design. As the documentation states:
http://download.oracle.com/docs/cd/E12839_01/integration.1111/e10224/bp_faults.htm#BABIGGIB
If a fault occurs during runtime in an invoke activity in a process, the framework catches the fault and performs a user-specified action defined in a fault policy file associated with the activity.
The fault management framework catches all faults (business and runtime) for an invoke activity.
So the above means that unless the fault is thrown in response to an invoke activity the Fault Policy set will not be triggered, which has been confirmed through the test you have uploaded. Please let me know if you have any questions or concerns.

"page fault in nonpaged area" BSOD when installing latest driver for M476dw

I just purchased a Color Laserjet MFP M476dw for use on my wireless network.
I downloaded the latest version of the driver suite from HP: LJPro-MFP-M476-Full-Solution-13302
for my OS Windows 8.1 / 64-bit listed as version: 10.0.13302.320 --   25 Sep 2014
I was logged in with a local Administrator level account for the install
I launched the install, the printer was discovered and s/w install went along fine until it got to the point of printing the test page ... the test page printed but as the page was printing the computer locked with its (first ever) BOSD:
"page fault in nonpaged area"
I powered down, rebooted and after login got an error message that said:
"HP Printer status and alerts has encountered and error and can not recover ... please restart ...
windows versoin: Win32NT 6.2.9200.0
HP Printer Status and Alerts version: 070.040.00169
I rebooted again and got the same error....
I launched the uninstaller program with the hopes of just uninstalling the printer status s/w and then reinstalling it,
but the uninstaller appears to have uninstalled the entire suite of s/w.....
Before I go at this again, I thought I'd ask for suggestions............
I've owned this laptop for 6 months, and it has been rocksolid ... this is the first BSOD I've experienced....
Thanks for any help!
This question was solved.
View Solution.

so .... having received no suggestions I figured I'd try re-installing withOUT installing the status monitor s/w option.
After unsellectin that, the rest of the driver package installed, and test page printed then I got a DIFFERENT BSod:
kernel_security_check_failure
Event log says:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000139 (0x0000000000000003, 0xffffd000beab77a0, 0xffffd000beab76f8, 0x0000000000000000). A dump was saved in: C:\windows\MEMORY.DMP. Report Id: 031715-9734-01.
Then next:
HPLaserJet Service:
Service cannot be started. System.BadImageFormatException: Could not load file or assembly 'HPTools, Version=8.12.1454.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The module was expected to contain an assembly manifest.
File name: 'HPTools, Version=8.12.1454.0, Culture=neutral, PublicKeyToken=null'
   at HPLaserJetService.HPLaserJetService.OnStart(String[] args)
   at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
the printer icon shows up in printers & devices, but will not print a test page..........
So ............ Uninstalled yet again, then rebooted and installed JUST the basic printer & scan drivers,
(i.e. the two "required" elements of the package)....
This works, so at least I can use my printer while I try to figure out the rest of this stuff..........
I'm pretty disappointed here ............
Any help would be much appreciated.............

Fault Handling a netbeans generated web service fault

Hi, we have been unsuccessful in creating a simple example where a bpel process could handle an exception thrown be a web service deployed in a EJBModule created in netbeans 5.5.
The fault handling of fault thrown be other bpel process seems to work fine, but in the case of a web service fault the process dies.
We come to realise that the soap message of a fault is different for a bpel thrown fault and a web service one. Dont know if it has something to do with the problem...
Note that there is no example of fault handling of a netbeans created webservice in a bpel process (at least we didn't find one).
Has someone been able to do this kind of fault handling?
Maybe someone could post a link to an example?
Any help is appreciated

What BPEL expects is a WS fault. The fault has to be defined on the WSDL operation that the BPEL invokes. If the EJB sent a soap fault, and that is the contract between the EJB and the BC, then i would say it is the resposibility of the SOAP BC to translate it into a WSDL operation defined fault and pass it on to the BPEL engine.
If the BC just hints that a fault has happened but doesn't give enough information that is necessary for the fault handling, the process will surely terminate.
If in the process you define a catchAll around the EJB invoke, you would be able to handle the fault from the BC.
I know of this one example, but not sure if they handle faults
http://blogs.sun.com/gopalan/page/gopalan?entry=ts_3175_building_a_service
The following link may be of some use.
https://blueprints.dev.java.net/bpcatalog/ee5/soa/

How to reduce page faults (virtual memory) usage in LabVIEW

I am running LabVIEW 2010 on Windows Embedded Standard system 4G (3G usable) of RAM.
The program (executable running on the Run-Time Engine) continuously samples from a USB-6251 at 1MS/sec (2 channels @ 500K) and scans the data stream for anomalous events, which are recorded to file. The system is intended to run 24/7 for at least 2 months, and although everything is working fine (6% CPU, no memory leaks), it generates 6000 Page Faults / second. I am concerned that I will kill the hard-drive at this rate, over long periods of time. There is plenty of RAM available (LabVIEW is only using 200K, and there is over 2G free), but the program is choosing to rely on Virtual Memory instead.
Is there a way to force (coerce) a LabVIEW application to consume more RAM and less VM?
The code is heavy (2 independent routines to collect and process the data stream through a shared double buffer, lots of in-obvious logic...), but I will post if it would help to answer the question.

Craig Akers wrote:
I am running LabVIEW 2010 on Windows Embedded Standard system 4G (3G usable) of RAM.
The program (executable running on the Run-Time Engine) continuously samples from a USB-6251 at 1MS/sec (2 channels @ 500K) and scans the data stream for anomalous events, which are recorded to file. The system is intended to run 24/7 for at least 2 months, and although everything is working fine (6% CPU, no memory leaks), it generates 6000 Page Faults / second. I am concerned that I will kill the hard-drive at this rate, over long periods of time. There is plenty of RAM available (LabVIEW is only using 200K, and there is over 2G free), but the program is choosing to rely on Virtual Memory instead.
Is there a way to force (coerce) a LabVIEW application to consume more RAM and less VM?
The code is heavy (2 independent routines to collect and process the data stream through a shared double buffer, lots of in-obvious logic...), but I will post if it would help to answer the question.
IIRC, the decision to move a page of memory from physical memory to disk is made at the OS level. There probably isn't any setting you can change in LabVIEW to change this behavior.
Keep in mind that not every page fault results in a page being loaded from disk. If your program (or the LabVIEW run-time) is frequently allocating and freeing memory, you could get a lot of soft page faults as the physical memory pages are repeatedly allocated to your process and returned to the OS. If you're only running at 6% CPU, this wouldn't be a problem.
You could try disabling the page file altogether, if the machine has enough RAM, but I wouldn't do this unless you actually have a performance (or hard-disk durability) problem. Having a page file to back up the physical memory is the difference between your program suffering from degraded performance vs. simply crashing if the machine runs out of physical memory.
Mark Moss
Electrical Validation Engineer
GHSP

Logical : paging out memory to disk.

Hi,
We have to reorg the table in production and so I tried to test in test database but everytime I issue move command , logical apply get stopped with error " paging out memory to disk". I tried to increare SGA and allocated more memory for LCR but think this is not a proper solution.
Can you guys suggest me any better way ? or do you think shall I use skip handler??
Thanks so much!

Hello,
Just re opening this thread since I am getting the same error in one my databases. DB version is 11.2.0.3 and my OS is RHEL 5, X86-64. My ulimit is set to "unlimited" for oracle user. I am seeing the following error and session is being terminated.
ORA-04030: out of process memory when trying to allocate 16408 bytes (QERHJ hash-joi,QERHJ Bit vector)
More info from incident files. Any hints will be appreciated. Thanks.
========= Dump for incident 360697 (ORA 4030) ========
----- Beginning of Customized Incident Dump(s) -----
=======================================
TOP 10 MEMORY USES FOR THIS PROCESS
*** 2012-12-04 14:29:30.744
52% 2719 MB, 1991346 chunks: "permanent memory "
qmxdGetChildNo ds=0x2ab9c31d9620 dsprt=0x2ab9c302dcd0
37% 1950 MB, 663782 chunks: "free memory "
qmxdGetChildNo ds=0x2ab9c31d9620 dsprt=0x2ab9c302dcd0
2% 111 MB, 2897152 chunks: "qmxdplsArrayGetNI1 "
qmxdpls_subhea ds=0x2ab8725ba6d0 dsprt=0x2ab86dbc27c0
2% 111 MB, 2897152 chunks: "qmxdplsArrayNI0 "
qmxdpls_subhea ds=0x2ab8725ba6d0 dsprt=0x2ab86dbc27c0
2% 101 MB, 29363 chunks: "permanent memory "
qmxlu subheap ds=0x2ab9c3031d10 dsprt=0x2ab8725ba6d0
2% 101 MB, 663782 chunks: "qmxdGetChildNodes-subheap "
qmxdpls_nodeli ds=0x2ab9c302dcd0 dsprt=0x2ab8725ba6d0
1% 59 MB, 3787 chunks: "pl/sql vc2 " PL/SQL
koh-kghu call ds=0x2ab86e1d23b0 dsprt=0xbb07ca0
1% 52 MB, 17734 chunks: "permanent memory "
ds=0x2ab9c3034780 dsprt=0x2ab8725ba6d0
1% 34 MB, 466 chunks: "free memory "
pga heap ds=0xbb07ca0 dsprt=(nil)
0% 23 MB, 1462 chunks: "pmucalm coll " PL/SQL
koh-kghu call ds=0x2ab86e1a11a0 dsprt=0xbb07ca0
=======================================
PRIVATE MEMORY SUMMARY FOR THIS PROCESS
PRIVATE HEAP SUMMARY DUMP
5454 MB total:
5420 MB commented, 635 KB permanent
34 MB free (31 MB in empty extents),
5335 MB, 1 heap: "session heap " 60 KB free held
==========================================
INSTANCE-WIDE PRIVATE MEMORY USAGE SUMMARY
Dumping Work Area Table (level=1)
=====================================
Global SGA Info
global target: 4096 MB
auto target: 256 MB
max pga: 819 MB
pga limit: 1638 MB
pga limit known: 0
pga limit errors: 0
pga inuse: 6581 MB
pga alloc: 7038 MB
pga freeable: 276 MB
pga freed: 2000919 MB
pga to free: 0 %
broker request: 0
pga auto: 20 MB
pga manual: 0 MB
pga alloc (max): 10338 MB
pga auto (max): 1039 MB
pga manual (max): 0 MB
# workareas : 0
# workareas(max): 80
================================
PER-PROCESS PRIVATE MEMORY USAGE
Private memory usage per Oracle process
Top 10 processes:
(percentage is of 7038 MB total allocated memory)
78% pid 81: 5420 MB used of 5457 MB allocated <= CURRENT PROC
7% pid 176: 300 MB used of 486 MB allocated (185 MB freeable)
1% pid 42: 48 MB used of 55 MB allocated (5952 KB freeable)
1% pid 36: 41 MB used of 44 MB allocated
1% pid 38: 41 MB used of 44 MB allocated (1088 KB freeable)
1% pid 41: 41 MB used of 44 MB allocated (1088 KB freeable)
1% pid 20: 10 MB used of 42 MB allocated (30 MB freeable)
0% pid 44: 5570 KB used of 33 MB allocated (1600 KB freeable)
0% pid 10: 28 MB used of 31 MB allocated (2304 KB freeable)
0% pid 73: 24 MB used of 26 MB allocated (1280 KB freeable)

Paging out despite "free" RAM

Today I was capturing HD video from my camera to iMovie when I noticed that my computer was "paging out." I was under the impression that if I had sufficient RAM that my computer would not need to page out. Here is the data from iStat pro:
Wired: 470 MB
Active: 661 MB
Inactive: 111 MB
Free: 3.79 GB
Swap: 15 MB/64 MB
Page ins: 68409
Page outs: 80
If I have 3.79 GB of free memory, why would it page out?

No, that's not correct. The OS constantly pages data to and from VM. Here's some relevant reading material that should help you better understand memory management:
About OS X Memory Management and Usage
Reading system memory usage in Activity Monitor
Memory Management in Mac OS X
Performance Guidelines- Memory Management in Mac OS X
A detailed look at memory usage in OS X
Understanding top output in the Terminal
The amount of available RAM for applications is the sum of Free RAM and Inactive RAM. This will change as applications are opened and closed or change from active to inactive status. The Swap figure represents an estimate of the total amount of swap space required for VM if used, but does not necessarily indicate the actual size of the existing swap file. If you are really in need of more RAM that would be indicated by how frequently the system uses VM. If you open the Terminal and run the top command at the prompt you will find information reported on Pageins () and Pageouts (). Pageouts () is the important figure. If the value in the parentheses is 0 (zero) then OS X is not making instantaneous use of VM which means you have adequate physical RAM for the system with the applications you have loaded. If the figure in parentheses is running positive and your hard drive is constantly being used (thrashing) then you need more physical RAM.

Page fault handler will be paged out

Similar Messages

Maybe you are looking for