Touchend event in javascript running in UIWebView creates memory leak

I have an iPhone app that has a UIWebView on the main view.
If I load a html page from the bundle that registers for the touchend event in javascript, each time the event is called it leaks memory.
I can even have the function that is called by the event be empty and it still leaks.
If I remove registering for the event then the leak never occurs.
Any ideas on how to fix prevent the leak?
Thanks!

I just discovered the same problem as you.
Did you ever find a solution to this problem?

Similar Messages

ListOfValues Cancel button creates memory leak

I believe one nuance of the listOfValues element (in an LOV page) gives rise to a memory leak. The examples and listOfValues documentation shows storing data needed by listOfValues events in the session. This is all fine and good if the user clicks on the "Select" button, as you get both a lovSelect and lovUpdate event to work with and clean out session data. But in the case of a user clicking the "Cancel" button, no event is fired, nor is a forward to another DataAction done. The window is simply closed. This strands all the data for the LOV (which could be quite sizable) in the user's session. You can't send this data on the request, because the LOV data must exist across several requests.
Am I completely missing something? How does one clean out a user's session when the Cancel button is clicked on a listOfValues component?
Brad

I am using JDeveloper 9.0.5.2. The restrictions of the project prevent using a newer version of JDeveloper. I am using ADF/Struts, and pure UIX (no JSPS).
The functionality I am speaking of is the standard behavior of the <listOfValues> component (lov for short). The lov component generates events for various behaviors (lovFilter, lovUpdate, loveSelect, etc.). It also completely encapsulates the Cancel and Select buttons, so you have no direct access to those. In order to manage an lov web page (presumably launched from an <lovInput> component on a previous page), the events need access to a certain collection of data (data for the table, max size, starting row, selection, validity, etc.). Because use of the lov page will result in potentially multiple submits, the request is not a good place to store this data, as the data needs to persist for the life of the lov page.
If you look at some of the lovInput/listOfValues examples on the OTN, you'll see that this data is persisted in the user's session. In and of itself, this is fine.
The problem is introduced by the fact that the lov's Cancel button (or window close) does not generate any events, and you don't have direct access to those controls to add an event of your own. When the cancel button is clicked, the window just closes, and in the words of the lov documentation "no other events occur."
This is very problematic -- your session is still stuffed full of data to support the lov. I am looking for a way to remove that data.
Frank -- in your post, you say:
"why can't you add an event to clean the session from the data?"
If you know how to add such an event -- one that fires when the Cancel button is clicked, please enlighten me. I would greatly appreciate it!
Thanks,
Brad

Do I need to worry about these event handlers in a grid from a memory leak perspective?

I'm pretty new to Flex and coudn't figure out how to add event handlers to inline item renderer components from the containing file script so I attached the listnerers simply as part of the components themselves (eg <mx:Checkbox ... chnage="outerDocument.doSomething(event)"../>):
<mx:DataGrid id="targetsGrid" width="100%" height="100%" doubleClickEnabled="true" styleName="itemCell"
      headerStyleName="headerRow" dataProvider="{targets}"
      rowHeight="19" fontSize="11" paddingBottom="0" paddingTop="1">
     <mx:columns>
     <mx:DataGridColumn width="78" dataField="@isSelected" headerText="">
     <mx:itemRenderer>
          <mx:Component>
               <mx:HBox width="100%" height="100%" horizontalAlign="center">
                    <mx:CheckBox id="targetCheckBox" selected="{data.@isSelected == 'true'}"
                         change="outerDocument.checkChangeHandler(event);"/>
                    <mx:Image horizontalAlign="center" toolTip="Delete" source="@Embed('/assets/icons/delete.png')" useHandCursor="true" buttonMode="true"
                         click="outerDocument.deleteHandler(event);"/>
                    <mx:Image id="editButton" horizontalAlign="center" toolTip="Edit" source="@Embed('/assets/icons/edit-icon.png')" useHandCursor="true" buttonMode="true"
                         click="outerDocument.editHandler(event);"/>
               </mx:HBox>
          </mx:Component>
     </mx:itemRenderer>
     </mx:DataGridColumn>
          <mx:DataGridColumn id="Name" dataField="@collectionDesc" headerText="Name" itemRenderer="com.foobar.integrated.media.ui.component.CellStyleForTargetName"/>
          <mx:DataGridColumn id="Created" width="140" dataField="@createDateTime" headerText="Created" labelFunction="UiHelper.gridDateFormat" />
     </mx:columns>
</mx:DataGrid>
This grid is part of a view that will get destroyed and recreated potentially many times during a user's session within the application (there's a large dynamic nature to the app and views are created at run-time.) By destroyed I mean that the view that holds the above datagrid will no longer be referenced under certain circumstances and an entire new view object is created (meaning the old datagrid is no longer refernced and a new one is created.)
I heard you should clean up event handlers when they are no longer used, and I know at what point the view is destroyed, but I don't know how to clean up the event handlers added to the item renderer components? Is it something that the Flex garbage collector will handle efficiently?
Also, on a somewhat related note, how could I push the item renderer to an external component since in my event handlers for the item renderer buttons I need a reference to the datagrid.selectedIndex which, as an external item renderer I wouldn't have access to this containing grid?

No. You don't need explicit cleanup in this case: if your outerDocument is going away, you have nothing to worry about. The event handler leak can happen in sort of the reverse situation: suppose you have a long-lived MyView that contains a custom DataGrid like the one below. Now suppose that MyView frequently destroys and re-creates the grid. And suppose that on its creationComplete event, the grid registers a listener for outerDocument's (MyView's) enterFrame Event. Unless you explicitly remove this listener, MyView will still have a reference to it even after the grid that registered the listener is destroyed (and garbage collected).
This is a pretty contrived example, but it sort of illustrates the potential for leaks: a certain component is elligible for garbage collection, but some longer-lived component holds a reference to it (or part of it, such as a listener function). If the longer-lived component is elligible for GC as well, you don't really need to worry about proper cleanup. That's what you're paying the GC processor cycles for.

What do I do if I get "Running out of Application Memory" when no applications are open except finder and just copying pictures to Seagate?

I cannot copy pictures to a Seagate as I get the out of memory notice with the only option to restart finder,repeatedly. I looked at older discussions and did not see a definitive fix, but many posted this, so I will as well:
Many discussions were too advanced for me. I have OS X 10.9.3
EtreCheck version: 1.9.12 (48)
Report generated July 23, 2014 at 11:57:23 AM EDT
Hardware Information:
MacBook Pro (13-inch, Mid 2010) (Verified)
MacBook Pro - model: MacBookPro7,1
1 2.66 GHz Intel Core 2 Duo CPU: 2 cores
8 GB RAM
Video Information:
NVIDIA GeForce 320M - VRAM: 256 MB
Color LCD 1280 x 800
System Software:
OS X 10.9.3 (13D65) - Uptime: 0 days 0:23:21
Disk Information:
APPLE SSD TS512B disk0 : (500.28 GB)
EFI (disk0s1) <not mounted>: 209.7 MB
Mac (disk0s2) / [Startup]: 399 GB (99.03 GB free)
Recovery HD (disk0s3) <not mounted>: 650 MB
BOOTCAMP (disk0s4) /Volumes/BOOTCAMP: 100.42 GB (70.82 GB free)
MATSHITADVD-R   UJ-898
USB Information:
Apple Inc. Built-in iSight
Apple Internal Memory Card Reader
Apple Inc. BRCM2046 Hub
Apple Inc. Bluetooth USB Host Controller
Apple Computer, Inc. IR Receiver
Apple Inc. Apple Internal Keyboard / Trackpad
Gatekeeper:
Mac App Store and identified developers
Kernel Extensions:
[not loaded] com.Belcarra.iokit.USBLAN_netpart (2.0.2) Support
[not loaded] com.Belcarra.iokit.USBLAN_usbpart (2.0.2) Support
[not loaded] com.RemoteControl.USBLAN.panther (1.6.1) Support
[not loaded] com.RemoteControl.USBLAN.usbpart (2.0.6) Support
[not loaded] com.belcarra.iokit.netpart.panther (1.6.1) Support
[not loaded] com.belcarra.iokit.usbpart.panther (1.6.1) Support
[loaded] com.logmein.driver.LogMeInSoundDriver (1.0.3 - SDK 10.5) Support
[not loaded] com.seagate.driver.PowSecDriverCore (5.2.6 - SDK 10.4) Support
[not loaded] com.seagate.driver.PowSecLeafDriver_10_4 (5.2.6 - SDK 10.4) Support
[not loaded] com.seagate.driver.PowSecLeafDriver_10_5 (5.2.6 - SDK 10.5) Support
[not loaded] com.seagate.driver.SeagateDriveIcons (5.2.6 - SDK 10.4) Support
[loaded] com.squirrels.airparrot.framebuffer (3 - SDK 10.7) Support
[loaded] com.squirrels.driver.AirParrotSpeakers (1.7 - SDK 10.7) Support
Problem System Launch Daemons:
[running] com.seagate.TBDecorator.plist Support
Launch Daemons:
[loaded] com.adobe.fpsaud.plist Support
[loaded] com.adobe.SwitchBoard.plist Support
[running] com.fitbit.galileod.plist Support
[loaded] com.google.keystone.daemon.plist Support
[not loaded] com.logmein.logmeinblanker.plist Support
[running] com.logmein.logmeinserver.plist Support
[loaded] com.logmein.raupdate.plist Support
[loaded] com.microsoft.office.licensing.helper.plist Support
[running] com.wyse.PocketCloud.plist Support
Launch Agents:
[not loaded] com.adobe.AAM.Updater-1.0.plist Support
[loaded] com.google.keystone.agent.plist Support
[failed] com.logmein.LMILaunchAgentFixer.plist Support
[running] com.logmein.logmeingui.plist Support
[running] com.logmein.logmeinguiagent.plist Support
[not loaded] com.logmein.logmeinguiagentatlogin.plist Support
[running] com.wyse.MacCompanion.plist Support
User Launch Agents:
[loaded] com.adobe.AAM.Updater-1.0.plist Support
[loaded] com.adobe.ARM.[...].plist Support
[running] com.google.Chrome.framework.plist Support
User Login Items:
Dropbox
Internet Plug-ins:
LogitechHarmony: Version: 1.0.0.1 Support
LogMeInSafari64: Version: 1.0.660 Support
Default Browser: Version: 537 - SDK 10.9
AdobeExManDetect: Version: AdobeExManDetect 1.1.0.0 - SDK 10.7 Support
Flip4Mac WMV Plugin: Version: 2.3.6.5 Support
AdobePDFViewerNPAPI: Version: 10.1.10 Support
FlashPlayer-10.6: Version: 14.0.0.145 - SDK 10.6 Support
LogMeIn: Version: 1.0.660 Support
Silverlight: Version: 5.1.10411.0 - SDK 10.6 Support
Flash Player: Version: 14.0.0.145 - SDK 10.6 Support
iPhotoPhotocast: Version: 7.0 - SDK 10.8
LogMeInSafari32: Version: 1.0.660 Support
QuickTime Plugin: Version: 7.7.3
AdobePDFViewer: Version: 10.1.10 Support
CANONiMAGEGATEWAYDL: Version: 3.1.0.2 Support
SharePointBrowserPlugin: Version: 14.1.4 - SDK 10.6 Support
JavaAppletPlugin: Version: 14.9.0 - SDK 10.7 Check version
Audio Plug-ins:
BluetoothAudioPlugIn: Version: 1.0 - SDK 10.9
AirPlay: Version: 2.0 - SDK 10.9
AppleAVBAudio: Version: 203.2 - SDK 10.9
iSightAudio: Version: 7.7.3 - SDK 10.9
iTunes Plug-ins:
Quartz Composer Visualizer: Version: 1.4 - SDK 10.9
3rd Party Preference Panes:
Flash Player Support
Flip4Mac WMV Support
Paragon NTFS for Mac ® OS X Support
Time Machine:
Skip System Files: NO
Mobile backups: ON
Auto backup: YES
Volumes being backed up:
Mac: Disk size: 371.60 GB Disk used: 279.37 GB
Destinations:
Untitled [Local]
Total size: 931.19 GB
Total number of backups: 30
Oldest backup: 2012-05-18 05:12:38 +0000
Last backup: 2014-07-14 18:51:50 +0000
Size of backup disk: Adequate
Backup size 931.19 GB > (Disk used 279.37 GB X 3)
Time Machine Backups [Local]
Total size: 2
Total number of backups: 26
Oldest backup: 2010-11-21 17:58:03 +0000
Last backup: 2014-07-14 19:53:01 +0000
Size of backup disk: Excellent
Backup size 2 > (Disk size 371.60 GB X 3)
Backups.backupdb [Network] (Last used)
Total size: 930.87 GB
Total number of backups: 32
Oldest backup: 2013-11-19 00:45:22 +0000
Last backup: 2014-07-15 15:36:23 +0000
Size of backup disk: Adequate
Backup size 930.87 GB > (Disk used 279.37 GB X 3)
Time Machine details may not be accurate.
All volumes being backed up may not be listed.
Top Processes by CPU:
      5% WindowServer
      0% fontd
      0% LogMeIn
      0% configd
      0% aosnotifyd
Top Processes by Memory:
115 MB mds_stores
98 MB Google Chrome
82 MB Finder
74 MB Dropbox
49 MB WindowServer
Virtual Memory Information:
4.65 GB Free RAM
1.43 GB Active RAM
1.00 GB Inactive RAM
675 MB Wired RAM
999 MB Page-ins
0 B Page-outs

Your problem is excessive swapping of data between physical memory and virtual memory.
That can happen for two reasons:
(1) You have a long-running process with a memory leak (i.e., a bug), or
(2) You don't have enough memory installed for your usage pattern.
Tracking down a memory leak can be difficult, and it may come down to a process of elimination. In Activity Monitor, select All Processes from the menu in the toolbar, if not already selected. Click the heading of the Real Mem column in the process table once or twice to sort the table with the highest value at the top. Repeat with the Virtual Mem column. If one process (not including "kernel_task") is using much more memory than all the others, that could be an indication of a leak. A better indication would be a process that continually grabs more and more memory over time without ever releasing it.
If you don't have an obvious memory leak, your options are to install more memory (if possible) or to run fewer programs simultaneously.

New iMac27" OS 10.9.4 runs out of application memory

I have a brand new iMac 27" with 1TB Flash drive, 16GB RAM, i7 processor 3.5Ghz
Although I only migrated the data files from an older iMac running Lion OS, I installed only a few apps fresh on the systems:MS office 2011, Skype, Chrome, Teamviewer and Firefox.
It was running for several days with only Mail and Safari open.
Time Machine was on for backup.
Suddenly it gave an error that application memory was full and the computer needed to restart.
This is odd.
Etrecheck report:
EtreCheck version: 1.9.12 (48)
Report generated August 6, 2014 at 11:07:07 AM PDT
Hardware Information:
iMac (27-inch, Late 2013) (Verified)
iMac - model: iMac14,2
1 3.5 GHz Intel Core i7 CPU: 4 cores
16 GB RAM
Video Information:
NVIDIA GeForce GTX 775M - VRAM: 2048 MB
iMac 2560 x 1440
System Software:
OS X 10.9.4 (13E28) - Uptime: 0 days 0:37:1
Disk Information:
APPLE SSD SM1024F disk0 : (1 TB)
EFI (disk0s1) <not mounted>: 209.7 MB
Macintosh HD (disk0s2) / [Startup]: 999.7 GB (726.5 GB free)
Recovery HD (disk0s3) <not mounted>: 650 MB
USB Information:
Apple Inc. FaceTime HD Camera (Built-in)
Apple Inc. BRCM20702 Hub
Apple Inc. Bluetooth USB Host Controller
Apple Inc. MacBook Air SuperDrive
FireWire Information:
OWC Mercury Elite-AL Pro unknown_device 400mbit - 400mbit max
EFI (disk1s1) <not mounted>: 209.7 MB
OWC Mercury Elite AL Pro (disk1s2) /Volumes/OWC Mercury Elite AL Pro: 999.86 GB (191.06 GB free)
Thunderbolt Information:
Apple Inc. thunderbolt_bus
Apple Inc. Thunderbolt to FireWire Adapter
Gatekeeper:
Mac App Store and identified developers
Launch Daemons:
[loaded] com.microsoft.office.licensing.helper.plist Support
[loaded] com.teamviewer.Helper.plist Support
[running] com.teamviewer.teamviewer_service.plist Support
Launch Agents:
[running] com.teamviewer.teamviewer.plist Support
[running] com.teamviewer.teamviewer_desktop.plist Support
User Launch Agents:
[loaded] com.google.keystone.agent.plist Support
User Login Items:
Microsoft AU Daemon
Mail
Internet Plug-ins:
Default Browser: Version: 537 - SDK 10.9
QuickTime Plugin: Version: 7.7.3
SharePointBrowserPlugin: Version: 14.1.0 Support
Audio Plug-ins:
BluetoothAudioPlugIn: Version: 1.0 - SDK 10.9
AirPlay: Version: 2.0 - SDK 10.9
AppleAVBAudio: Version: 203.2 - SDK 10.9
iSightAudio: Version: 7.7.3 - SDK 10.9
iTunes Plug-ins:
Quartz Composer Visualizer: Version: 1.4 - SDK 10.9
User Internet Plug-ins:
WebEx: Version: 1.0 Support
3rd Party Preference Panes:
None
Time Machine:
Auto backup: YES
Volumes being backed up:
Macintosh HD: Disk size: 931.04 GB Disk used: 254.43 GB
Destinations:
OWC Mercury Elite AL Pro [Local] (Last used)
Total size: 931.19 GB
Total number of backups: 30
Oldest backup: 2014-08-01 03:42:38 +0000
Last backup: 2014-08-06 17:22:42 +0000
Size of backup disk: Adequate
Backup size 931.19 GB > (Disk used 254.43 GB X 3)
Time Machine details may not be accurate.
All volumes being backed up may not be listed.
Top Processes by CPU:
      53% TeamViewer_Desktop
      11% WindowServer
      1% TeamViewer_Service
      1% fontd
      0% coreservicesd
Top Processes by Memory:
573 MB Mail
324 MB TeamViewer_Desktop
197 MB WindowServer
164 MB mds_stores
115 MB com.apple.IconServicesAgent
Virtual Memory Information:
11.49 GB Free RAM
2.21 GB Active RAM
923 MB Inactive RAM
1.39 GB Wired RAM
1.49 GB Page-ins
0 B Page-outs
Seems odd that a brand new computer less than a week old would give this error. Any suggestions?

There is excessive swapping of data between physical memory (that is, the memory chips on the logic board) and virtual memory (one or more files on the startup volume.) That activity is relatively slow and causes the whole system to be less responsive. It can happen for two reasons:
          A long-running process with a memory leak (a kind of bug)
          Not enough memory for your usage pattern
Tracking down a memory leak can be difficult, and it may come down to a process of elimination.
These instructions are for OS X 10.9 ("Mavericks.") The procedure may be slightly different for earlier versions of OS X.
When you notice the swap activity, open the Activity Monitor application and select All Processes from the View menu, if it's not already selected. Select the Memory tab. Click the heading of the Real Mem column in the process table twice to sort the table with the highest value at the top. If you don't see that column, select
          View ▹ Columns ▹ Real Memory
from the menu bar.
If one process (excluding "kernel_task") is using much more memory than all the others, that could be an indication of a leak. A better indication would be a process that continually grabs more and more real memory over time without ever releasing it. Here is an example of how it's done.
The processes named "Safari Web Content" render web pages for Safari. They use a lot of memory and may leak if certain Safari extensions or third-party web plugins are installed. Consider them prime suspects.
Another process often implicated in memory leaks is "inkjet4" or "inkjet8," which is a component of the HP printing software. If it's present, force-quit the process in Activity Monitor to solve the problem temporarily. Empty the print queues in the Printers & Scanners preference pane (which has a slightly different name in each recent version of OS X.) If you don't use an HP printer, remove the software. Otherwise, if the problem is recurrent, update the software (which may not help) or contact HP support.
"Wired" memory should be a small part of the total. That memory is not swapped, but it makes less physical memory available which may then result in swapping. If you have a lot of wired memory, that's usually an indication of a memory leak in a third-party program that modifies the operating system at a low level. Ask for guidance in that case.
If you don't have an obvious memory leak, your options are to install more memory (if possible) or to run fewer programs simultaneously.
The next suggestion is only for users familiar with the shell. For a more precise, but potentially misleading, test, run the following command:
sudo leaks -nocontext -nostacks process | grep total
where process is the name of a process you suspect of leaking memory. Almost every process will leak some memory; the question is how much, and especially how much the leak increases with time. I can’t be more specific. See the leaks(1) man page and the Apple developer documentation for details.

How do i resolve an issue where i have run out of application memory?

My imac says i have run out of application memory and that i should quit applications. How do i resolve this issue?

The message has nothing to do with low disk space.
There is excessive swapping of data between physical memory (that is, the memory chips on the logic board) and virtual memory (one or more files on the startup volume.) That activity is relatively slow and causes the whole system to be less responsive. It can happen for two reasons:
A long-running process with a memory leak (a kind of bug)
Not enough memory for your usage pattern
Tracking down a memory leak can be difficult, and it may come down to a process of elimination.
These instructions are for OS X 10.9 ("Mavericks.") The procedure may be slightly different for earlier versions of OS X.
When you notice the swap activity, open the Activity Monitor application and select All Processes from the View menu, if it's not already selected. Select the Memory tab. Click the heading of the Real Mem column in the process table twice to sort the table with the highest value at the top. If you don't see that column, select
View ▹ Columns ▹ Real Memory
from the menu bar.
If one process (excluding "kernel_task") is using much more memory than all the others, that could be an indication of a leak. A better indication would be a process that continually grabs more and more real memory over time without ever releasing it. Here is an example of how it's done.
The processes named "Safari Web Content" render web pages for Safari. They use a lot of memory and may leak if certain Safari extensions or third-party web plugins are installed. Consider them prime suspects.
Another process often implicated in memory leaks is "inkjet4" or "inkjet8," which is a component of the HP printing software. If it's present, force-quit the process in Activity Monitor to solve the problem temporarily. Empty the print queues in the Printers & Scanners preference pane (which has a slightly different name in each recent version of OS X.) If you don't use an HP printer, remove the software. Otherwise, if the problem is recurrent, update the software (which may not help) or contact HP support.
"Wired" memory should be a small part of the total. That memory is not swapped, but it makes less physical memory available which may then result in swapping. If you have a lot of wired memory, that's usually an indication of a memory leak in a third-party program that modifies the operating system at a low level. Ask for guidance in that case.
If you don't have an obvious memory leak, your options are to install more memory (if possible) or to run fewer programs simultaneously.
The next suggestion is only for users familiar with the shell. For a more precise, but potentially misleading, test, run the following command:
sudo leaks -nocontext -nostacks process | grep total
where process is the name of a process you suspect of leaking memory. Almost every process will leak some memory; the question is how much, and especially how much the leak increases with time. I can’t be more specific. See the leaks(1) man page and the Apple developer documentation for details.

Mavericks has run out of application memory

Is there a fix for this yet? I've read a lot of threads full of conjecture.
Thanks.

There is excessive swapping of data between physical memory (that is, the memory chips on the logic board) and virtual memory (one or more files on the startup volume.) That activity is relatively slow and causes the whole system to be less responsive. It can happen for two reasons:
A long-running process with a memory leak (a kind of bug)
Not enough memory for your usage pattern
Tracking down a memory leak can be difficult, and it may come down to a process of elimination.
These instructions are for OS X 10.9 ("Mavericks.") The procedure may be slightly different for earlier versions of OS X.
When you notice the swap activity, open the Activity Monitor application and select All Processes from the View menu, if it's not already selected. Select the Memory tab. Click the heading of the Real Mem column in the process table twice to sort the table with the highest value at the top. If you don't see that column, select
View ▹ Columns ▹ Real Memory
from the menu bar.
If one process (excluding "kernel_task") is using much more memory than all the others, that could be an indication of a leak. A better indication would be a process that continually grabs more and more real memory over time without ever releasing it. Here is an example of how it's done.
The processes named "Safari Web Content" render web pages for Safari. They use a lot of memory and may leak if certain Safari extensions or third-party web plugins are installed. Consider them prime suspects.
Another process often implicated in memory leaks is "inkjet4" or "inkjet8," which is a component of the HP printing software. If it's present, force-quit the process in Activity Monitor to solve the problem temporarily. Empty the print queues in the Printers & Scanners preference pane (which has a slightly different name in each recent version of OS X.) If you don't use an HP printer, remove the software. Otherwise, if the problem is recurrent, update the software (which may not help) or contact HP support.
"Wired" memory should be a small part of the total. That memory is not swapped, but it makes less physical memory available which may then result in swapping. If you have a lot of wired memory, that's usually an indication of a memory leak in a third-party program that modifies the operating system at a low level. Ask for guidance in that case.
If you don't have an obvious memory leak, your options are to install more memory (if possible) or to run fewer programs simultaneously.
The next suggestion is only for users familiar with the shell. For a more precise, but potentially misleading, test, run the following command:
sudo leaks -nocontext -nostacks process | grep total
where process is the name of a process you suspect of leaking memory. Almost every process will leak some memory; the question is how much, and especially how much the leak increases with time. I can’t be more specific. See the leaks(1) man page and the Apple developer documentation for details.

Your system run out of application memory

your system run out of application memory i get this message pop up and everything freezes

There is excessive swapping of data between physical memory (that is, the memory chips on the logic board) and virtual memory (one or more files on the startup volume.) That activity is relatively slow and causes the whole system to be less responsive. It can happen for two reasons:
          A long-running process with a memory leak (a kind of bug)
          Not enough memory for your usage pattern
Tracking down a memory leak can be difficult, and it may come down to a process of elimination.
These instructions are for OS X 10.9 ("Mavericks.") The procedure may be slightly different for earlier versions of OS X.
When you notice the swap activity, open the Activity Monitor application and select All Processes from the View menu, if it's not already selected. Select the Memory tab. Click the heading of the Real Mem column in the process table twice to sort the table with the highest value at the top. If you don't see that column, select
          View ▹ Columns ▹ Real Memory
from the menu bar.
If one process (excluding "kernel_task") is using much more memory than all the others, that could be an indication of a leak. A better indication would be a process that continually grabs more and more real memory over time without ever releasing it. Here is an example of how it's done.
The processes named "Safari Web Content" render web pages for Safari. They use a lot of memory and may leak if certain Safari extensions or third-party web plugins are installed. Consider them prime suspects.
Another process often implicated in memory leaks is "inkjet4" or "inkjet8," which is a component of the HP printing software. If it's present, force-quit the process in Activity Monitor to solve the problem temporarily. Empty the print queues in the Printers & Scanners preference pane (which has a slightly different name in each recent version of OS X.) If you don't use an HP printer, remove the software. Otherwise, if the problem is recurrent, update the software (which may not help) or contact HP support.
"Wired" memory should be a small part of the total. That memory is not swapped, but it makes less physical memory available which may then result in swapping. If you have a lot of wired memory, that's usually an indication of a memory leak in a third-party program that modifies the operating system at a low level. Ask for guidance in that case.
If you don't have an obvious memory leak, your options are to install more memory (if possible) or to run fewer programs simultaneously.
The next suggestion is only for users familiar with the shell. For a more precise, but potentially misleading, test, run the following command:
sudo leaks -nocontext -nostacks process | grep total
where process is the name of a process you suspect of leaking memory. Almost every process will leak some memory; the question is how much, and especially how much the leak increases with time. I can’t be more specific. See the leaks(1) man page and the Apple developer documentation for details.

I'm getting the message that my MacBook Pro has run out of application memory?

If I'm not paying attention and am running more then 1 application at the same time I get a message that I've run out of application memory and need to "force quit" current applications in order to continue. Anything I can do to resolve this problem like add more RAM/

First, all so-called "memory cleaning" software is worse than useless.
There is excessive swapping of data between physical memory (that is, the memory chips on the logic board) and virtual memory (one or more files on the startup volume.) That activity is relatively slow and causes the whole system to be less responsive. It can happen for two reasons:
          A long-running process with a memory leak (a kind of bug)
          Not enough memory for your usage pattern
Please note that if the cause is a memory leak, installing more memory will not help. That's likely if you already have more than 4 GB of memory. Tracking down a memory leak can be difficult, and it may come down to a process of elimination.
These instructions are for OS X 10.9 and later. Some details may be slightly different for earlier versions of OS X.
When you notice the swap activity, open the Activity Monitor application and select All Processes from the View menu, if it's not already selected. Select the Memory tab. Click the heading of the Real Mem column in the process table twice to sort the table with the highest value at the top. If you don't see that column, select
          View ▹ Columns ▹ Real Memory
from the menu bar.
If one process (excluding "kernel_task") is using much more memory than all the others, that could be an indication of a leak. A better indication would be a process that continually grabs more and more real memory over time without ever releasing it. Here is an example of how it's done.
The processes named "Safari Web Content" render web pages for Safari. They use a lot of memory and may leak if certain Safari extensions or third-party web plugins are installed. Consider them prime suspects.
Another process often implicated in memory leaks is "inkjet4" or "inkjet8," which is a component of the HP printing software. If it's present, force-quit the process in Activity Monitor to solve the problem temporarily. Empty the print queues in the Printers & Scanners preference pane (which has a slightly different name in each recent version of OS X.) If you don't use an HP printer, reset the printing system. Otherwise, if the problem is recurrent, update the software (which may not help) or contact HP support.
"Wired" memory should be a small part of the total. That memory is not swapped, but it makes less physical memory available which may then result in swapping. If you have a lot of wired memory, that's usually an indication of a memory leak in a third-party program that modifies the operating system at a low level. Ask for guidance in that case.
If you don't have an obvious memory leak, your options are to install more memory (if possible) or to run fewer programs simultaneously.
The next suggestion is only for users familiar with the shell. For a more precise, but potentially misleading, test, run the following command:
sudo leaks -nocontext -nostacks process | grep total
where process is the name of a process you suspect of leaking memory. Almost every process will leak some memory; the question is how much, and especially how much the leak increases with time. I can’t be more specific. See the leaks(1) man page and the Apple developer documentation for details.

"Your system has run out of application memory"! Help, please! Thanks!

Hi,
Just got the unsettling message saying "Your system has run out of application memory" and I was instructed to close down applications I wasn't using, including browsers, or I might have problems with my computer. Yeesh. This is scary. Is the solution to buy more RAM? Bear with me, I really don't know what to do, and I'd appreciate your help.
Thanks,
Kcat
Tried to update my product listings, but it wouldn't work. I have OS X Mavericks, 10.9.2 on my iMac desktop.

There is excessive swapping of data between physical memory (that is, the memory chips on the logic board) and virtual memory (one or more files on the startup volume.) That activity is relatively slow and causes the whole system to be less responsive. It can happen for two reasons:
A long-running process with a memory leak (a kind of bug)
Not enough memory for your usage pattern
Tracking down a memory leak can be difficult, and it may come down to a process of elimination.
These instructions are for OS X 10.9 ("Mavericks.") The procedure may be slightly different for earlier versions of OS X.
When you notice the swap activity, open the Activity Monitor application and select All Processes from the View menu, if it's not already selected. Select the Memory tab. Click the heading of the Real Mem column in the process table twice to sort the table with the highest value at the top. If you don't see that column, select
View ▹ Columns ▹ Real Memory
from the menu bar.
If one process (excluding "kernel_task") is using much more memory than all the others, that could be an indication of a leak. A better indication would be a process that continually grabs more and more real memory over time without ever releasing it. Here is an example of how it's done.
The processes named "Safari Web Content" render web pages for Safari. They use a lot of memory and may leak if certain Safari extensions or third-party web plugins are installed. Consider them prime suspects.
Another process often implicated in memory leaks is "inkjet4" or "inkjet8," which is a component of the HP printing software. If it's present, force-quit the process in Activity Monitor to solve the problem temporarily. Empty the print queues in the Printers & Scanners preference pane (which has a slightly different name in each recent version of OS X.) If you don't use an HP printer, remove the software. Otherwise, if the problem is recurrent, update the software (which may not help) or contact HP support.
"Wired" memory should be a small part of the total. That memory is not swapped, but it makes less physical memory available which may then result in swapping. If you have a lot of wired memory, that's usually an indication of a memory leak in a third-party program that modifies the operating system at a low level. Ask for guidance in that case.
If you don't have an obvious memory leak, your options are to install more memory (if possible) or to run fewer programs simultaneously.
The next suggestion is only for users familiar with the shell. For a more precise, but potentially misleading, test, run the following command:
sudo leaks -nocontext -nostacks process | grep total
where process is the name of a process you suspect of leaking memory. Almost every process will leak some memory; the question is how much, and especially how much the leak increases with time. I can’t be more specific. See the leaks(1) man page and the Apple developer documentation for details.

"You system has run out of application memory"

I'm constantly getting this error now. "You system has run out of application memory"
machine specs are -
MACBookPro Retina. 10,1
2.7 i7
16 GB 1600 MHz DDR3
GT 650M 1024 MB
OSX 10.9.4 (13E28)
750 GB Solid State drive with 211 GB free.
does any know what may being going on? What can I do to fix?
Thanks in advance for your help.
Brian

There is excessive swapping of data between physical memory (that is, the memory chips on the logic board) and virtual memory (one or more files on the startup volume.) That activity is relatively slow and causes the whole system to be less responsive. It can happen for two reasons:
          A long-running process with a memory leak (a kind of bug)
          Not enough memory for your usage pattern
Tracking down a memory leak can be difficult, and it may come down to a process of elimination.
These instructions are for OS X 10.9 ("Mavericks.") The procedure may be slightly different for earlier versions of OS X.
When you notice the swap activity, open the Activity Monitor application and select All Processes from the View menu, if it's not already selected. Select the Memory tab. Click the heading of the Real Mem column in the process table twice to sort the table with the highest value at the top. If you don't see that column, select
          View ▹ Columns ▹ Real Memory
from the menu bar.
If one process (excluding "kernel_task") is using much more memory than all the others, that could be an indication of a leak. A better indication would be a process that continually grabs more and more real memory over time without ever releasing it. Here is an example of how it's done.
The processes named "Safari Web Content" render web pages for Safari. They use a lot of memory and may leak if certain Safari extensions or third-party web plugins are installed. Consider them prime suspects.
Another process often implicated in memory leaks is "inkjet4" or "inkjet8," which is a component of the HP printing software. If it's present, force-quit the process in Activity Monitor to solve the problem temporarily. Empty the print queues in the Printers & Scanners preference pane (which has a slightly different name in each recent version of OS X.) If you don't use an HP printer, remove the software. Otherwise, if the problem is recurrent, update the software (which may not help) or contact HP support.
"Wired" memory should be a small part of the total. That memory is not swapped, but it makes less physical memory available which may then result in swapping. If you have a lot of wired memory, that's usually an indication of a memory leak in a third-party program that modifies the operating system at a low level. Ask for guidance in that case.
If you don't have an obvious memory leak, your options are to install more memory (if possible) or to run fewer programs simultaneously.
The next suggestion is only for users familiar with the shell. For a more precise, but potentially misleading, test, run the following command:
sudo leaks -nocontext -nostacks process | grep total
where process is the name of a process you suspect of leaking memory. Almost every process will leak some memory; the question is how much, and especially how much the leak increases with time. I can’t be more specific. See the leaks(1) man page and the Apple developer documentation for details.

How do I fix message "computer has run out of application memory" even tho all apps are closed

Since loading Mavericks my iMac 27-inch (2009) 2.8 GHz Intel Core i7 4 GB 1067 MHz DDR3 stays almost out of virtual memory and often pauses all apps and messages "computer has run out of application memory." I have run spindump, but no significant difference is made.

Spindump is a diagnostic tool used by Apple. It doesn't fix anything.
There is excessive swapping of data between physical memory (that is, the memory chips on the logic board) and virtual memory (one or more files on the startup volume.) That activity is relatively slow and causes the whole system to be less responsive. It can happen for two reasons:
A long-running process with a memory leak (a kind of bug)
Not enough memory for your usage pattern
Tracking down a memory leak can be difficult, and it may come down to a process of elimination.
When you notice the swap activity, open the Activity Monitor application and select All Processes from the menu in the toolbar, if it's not already selected. Click the heading of the Real Mem column in the process table twice to sort the table with the highest value at the top. If you don't see that column, select
View ▹ Columns ▹ Real Memory
from the menu bar.
If one process (excluding "kernel_task") is using much more memory than all the others, that could be an indication of a leak. A better indication would be a process that continually grabs more and more real memory over time without ever releasing it. Here is an example of how it's done.
The process named "Safari Web Content" renders web pages for Safari and other applications. It uses a lot of memory and may leak if certain Safari extensions or third-party web plugins are installed. Consider it a prime suspect.
Another process often implicated in memory leaks is "inkjet4" or "inkjet8," which is a component of the HP printing software. If it's present, force-quit the process in Activity Monitor to solve the problem temporarily. Empty the print queues in the Printers & Scanners preference pane (which has a slightly different name in each recent version of OS X.) If you don't use an HP printer, remove the software. Otherwise, if the problem is recurrent, update the software (which may not help) or contact HP support.
The System Memory tab of the Activity Monitor window shows how physical memory is being used. "Wired" memory should be a small part of the total. That memory is not swapped, but it makes less physical memory available which may then result in swapping. If you have a lot of wired memory, that's usually an indication of a memory leak in a third-party program that modifies the operating system at a low level. Ask for guidance in that case.
If you don't have an obvious memory leak, your options are to install more memory (if possible) or to run fewer programs simultaneously.
The next suggestion is only for users familiar with the shell. For a more precise, but potentially misleading, test, run the following command:
sudo leaks -nocontext -nostacks process | grep total
where process is the name of a process you suspect of leaking memory. Almost every process will leak some memory; the question is how much, and especially how much the leak increases with time. I can’t be more specific. See the leaks(1) man page and the Apple developer documentation for details.

What can I do when it says "your system has run out of application memory?

What can I do when it says "your system has run out of application memory?"

The message has nothing to do with low disk space.
There is excessive swapping of data between physical memory (that is, the memory chips on the logic board) and virtual memory (one or more files on the startup volume.) That activity is relatively slow and causes the whole system to be less responsive. It can happen for two reasons:
          A long-running process with a memory leak (a kind of bug)
          Not enough memory for your usage pattern
Tracking down a memory leak can be difficult, and it may come down to a process of elimination.
These instructions are for OS X 10.9 ("Mavericks.") The procedure may be slightly different for earlier versions of OS X.
When you notice the swap activity, open the Activity Monitor application and select All Processes from the View menu, if it's not already selected. Select the Memory tab. Click the heading of the Real Mem column in the process table twice to sort the table with the highest value at the top. If you don't see that column, select
          View ▹ Columns ▹ Real Memory
from the menu bar.
If one process (excluding "kernel_task") is using much more memory than all the others, that could be an indication of a leak. A better indication would be a process that continually grabs more and more real memory over time without ever releasing it. Here is an example of how it's done.
The processes named "Safari Web Content" render web pages for Safari. They use a lot of memory and may leak if certain Safari extensions or third-party web plugins are installed. Consider them prime suspects.
Another process often implicated in memory leaks is "inkjet4" or "inkjet8," which is a component of the HP printing software. If it's present, force-quit the process in Activity Monitor to solve the problem temporarily. Empty the print queues in the Printers & Scanners preference pane (which has a slightly different name in each recent version of OS X.) If you don't use an HP printer, remove the software. Otherwise, if the problem is recurrent, update the software (which may not help) or contact HP support.
"Wired" memory should be a small part of the total. That memory is not swapped, but it makes less physical memory available which may then result in swapping. If you have a lot of wired memory, that's usually an indication of a memory leak in a third-party program that modifies the operating system at a low level. Ask for guidance in that case.
If you don't have an obvious memory leak, your options are to install more memory (if possible) or to run fewer programs simultaneously.
The next suggestion is only for users familiar with the shell. For a more precise, but potentially misleading, test, run the following command:
sudo leaks -nocontext -nostacks process | grep total
where process is the name of a process you suspect of leaking memory. Almost every process will leak some memory; the question is how much, and especially how much the leak increases with time. I can’t be more specific. See the leaks(1) man page and the Apple developer documentation for details.

My imac is saying it has run out of application memory. What do I do?

What do I do for this issue--my iMac (less than 1 year old) is saying that it has run out of application memory. Does this mean that I have to delete a bunch of applications? It's running really slow and crashes all the time now and says the applications are "paused" and I need to force quit them.

There is excessive swapping of data between physical memory (that is, the memory chips on the logic board) and virtual memory (one or more files on the startup volume.) That activity is relatively slow and causes the whole system to be less responsive. It can happen for two reasons:
A long-running process with a memory leak (a kind of bug)
Not enough memory for your usage pattern
Tracking down a memory leak can be difficult, and it may come down to a process of elimination.
These instructions are for OS X 10.9 ("Mavericks.") The procedure may be slightly different for earlier versions of OS X.
When you notice the swap activity, open the Activity Monitor application and select All Processes from the View menu, if it's not already selected. Select the Memory tab. Click the heading of the Real Mem column in the process table twice to sort the table with the highest value at the top. If you don't see that column, select
View ▹ Columns ▹ Real Memory
from the menu bar.
If one process (excluding "kernel_task") is using much more memory than all the others, that could be an indication of a leak. A better indication would be a process that continually grabs more and more real memory over time without ever releasing it. Here is an example of how it's done.
The processes named "Safari Web Content" render web pages for Safari. They use a lot of memory and may leak if certain Safari extensions or third-party web plugins are installed. Consider them prime suspects.
Another process often implicated in memory leaks is "inkjet4" or "inkjet8," which is a component of the HP printing software. If it's present, force-quit the process in Activity Monitor to solve the problem temporarily. Empty the print queues in the Printers & Scanners preference pane (which has a slightly different name in each recent version of OS X.) If you don't use an HP printer, remove the software. Otherwise, if the problem is recurrent, update the software (which may not help) or contact HP support.
"Wired" memory should be a small part of the total. That memory is not swapped, but it makes less physical memory available which may then result in swapping. If you have a lot of wired memory, that's usually an indication of a memory leak in a third-party program that modifies the operating system at a low level. Ask for guidance in that case.
If you don't have an obvious memory leak, your options are to install more memory (if possible) or to run fewer programs simultaneously.
The next suggestion is only for users familiar with the shell. For a more precise, but potentially misleading, test, run the following command:
sudo leaks -nocontext -nostacks process | grep total
where process is the name of a process you suspect of leaking memory. Almost every process will leak some memory; the question is how much, and especially how much the leak increases with time. I can’t be more specific. See the leaks(1) man page and the Apple developer documentation for details.

Running out of virtual memory

How do I increase the virtual memory? My Mac is running slow and seems to be bogging down at times. Can/will anyone help?
Thankx in advance
Marquis

It probably said you were running out of application memory.
There is excessive swapping of data between physical memory (that is, the memory chips on the logic board) and virtual memory (one or more files on the startup volume.) That activity is relatively slow and causes the whole system to be less responsive. It can happen for two reasons:
          A long-running process with a memory leak (a kind of bug)
          Not enough memory for your usage pattern
Tracking down a memory leak can be difficult, and it may come down to a process of elimination.
These instructions are for OS X 10.9 and later. Some details may be slightly different for earlier versions of OS X.
When you notice the swap activity, open the Activity Monitor application and select All Processes from the View menu, if it's not already selected. Select the Memory tab. Click the heading of the Real Mem column in the process table twice to sort the table with the highest value at the top. If you don't see that column, select
          View ▹ Columns ▹ Real Memory
from the menu bar.
If one process (excluding "kernel_task") is using much more memory than all the others, that could be an indication of a leak. A better indication would be a process that continually grabs more and more real memory over time without ever releasing it. Here is an example of how it's done.
The processes named "Safari Web Content" render web pages for Safari. They use a lot of memory and may leak if certain Safari extensions or third-party web plugins are installed. Consider them prime suspects.
Another process often implicated in memory leaks is "inkjet4" or "inkjet8," which is a component of the HP printing software. If it's present, force-quit the process in Activity Monitor to solve the problem temporarily. Empty the print queues in the Printers & Scanners preference pane (which has a slightly different name in each recent version of OS X.) If you don't use an HP printer, remove the software. Otherwise, if the problem is recurrent, update the software (which may not help) or contact HP support.
"Wired" memory should be a small part of the total. That memory is not swapped, but it makes less physical memory available which may then result in swapping. If you have a lot of wired memory, that's usually an indication of a memory leak in a third-party program that modifies the operating system at a low level. Ask for guidance in that case.
If you don't have an obvious memory leak, your options are to install more memory (if possible) or to run fewer programs simultaneously.
The next suggestion is only for users familiar with the shell. For a more precise, but potentially misleading, test, run the following command:
sudo leaks -nocontext -nostacks process | grep total
where process is the name of a process you suspect of leaking memory. Almost every process will leak some memory; the question is how much, and especially how much the leak increases with time. I can’t be more specific. See the leaks(1) man page and the Apple developer documentation for details.

Touchend event in javascript running in UIWebView creates memory leak

Similar Messages

Maybe you are looking for