Low memory startup disk

Computer very slow or freezes when running 2 programs at the same time. popup: memory low on startup disk. what can i do????? please!!!!

Delete some of the Junk files you have on the hard drive.

Similar Messages

Clear startup disk

I have received a warning that there is no room on my startup disk and that it is full. How do I delete things from it? I am having issues with photo storage - I purchased an external hard drive and saved all of my photos to it. I then deleted most of my photos from the computer. Today, however when importing photos (a fraction of what was removed) my computer notified me it was low on startup disk space and then an hour later (no additional photos saved to computer) that it was full. What is going on here? If anyone has a clue and thinks they can help, I would be much obliged!

For information about the Other category in the Storage display, see this support article. If the Storage display seems to be inaccurate, try rebuilding the Spotlight index.
Empty the Trash if you haven't already done so. If you use iPhoto, empty its internal Trash first:
iPhoto ▹ Empty Trash
Do the same in other applications, such as Aperture, that have an internal Trash feature. Then reboot. That will temporarily free up some space.
According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation. You also need enough space left over to allow for growth of the data. There is little or no performance advantage to having more available space than the minimum Apple recommends. Available storage space that you'll never use is wasted space.
When Time Machine backs up a portable Mac, some of the free space will be used to make local snapshots, which are backup copies of recently deleted files. The space occupied by local snapshots is reported as available by the Finder, and should be considered as such. In the Storage display of System Information, local snapshots are shown as Backups. The snapshots are automatically deleted when they expire or when free space falls below a certain level. You ordinarily don't need to, and should not, delete local snapshots yourself. If you followed bad advice to disable local snapshots by running a shell command, you may have ended up with a lot of data in the Other category. Reboot and it should go away.
See this support article for some simple ways to free up storage space.
You can more effectively use a tool such as OmniDiskSweeper (ODS) or GrandPerspective (GP) to explore the volume and find out what's taking up the space. You can also delete files with it, but don't do that unless you're sure that you know what you're deleting and that all data is safely backed up. That means you have multiple backups, not just one. Note that ODS only works with OS X 10.8 or later. If you're running an older OS version, use GP.
Deleting files inside an iPhoto or Aperture library will corrupt the library. Any changes to a photo library must be made from within the application that created it. The same goes for Mail files.
Proceed further only if the problem isn't solved by the above steps.
ODS or GP can't see the whole filesystem when you run it just by double-clicking; it only sees files that you have permission to read. To see everything, you have to run it as root.
Back up all data now.
If you have more than one user account, make sure you're logged in as an administrator. The administrator account is the one that was created automatically when you first set up the computer.
Install the app you downloaded in the Applications folder as usual. Quit it if it's running.
Triple-click anywhere in the corresponding line of text below on this page to select it, then copy the selected text to the Clipboard by pressing the key combination command-C:
sudo /Applications/OmniDiskSweeper.app/Contents/MacOS/OmniDiskSweeper
sudo /Applications/GrandPerspective.app/Contents/MacOS/GrandPerspective
Launch the built-in Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window (command-V). You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning to be careful. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
The application window will open, eventually showing all files in all folders, sorted by size. It may take a few minutes for the app to finish scanning.
I don't recommend that you make a habit of doing this. Don't delete anything as root. If something needs to be deleted, make sure you know what it is and how it got there, and then delete it by other, safer, means. When in doubt, leave it alone or ask for guidance.
When you're done with the app, quit it and also quit Terminal.

Startup Disk Memory Inexplicably Low/Missing

I normally keep a close eye on the amount of info going into my partitioned Mac HD (presently: capacity 29.88 GB, 27.64 Used, 2.23 Available), but I received a message today to the effect that "your startup disk is low in available memory..." while only running Safari... The last time I had checked (about 1 month ago) I had between 9 and 10 GB of available space, so needless to say I was rather surprised to get this message. I immediately did a "Get Info" on the drive and was SHOCKED for TWO reasons! 1) that the available memory was so low... but ALSO as I checked and RE-checked the memory was DISAPPEARING before my eyes! I was only running Safari (although a couple hours prior I had worked on and saved a 5+ page site in iWeb with a fair amount of imagery... I have 1 GB of RAM. I restarted and the drive has since stabalized at 2.22-2.23 GB Available. I restarted in Safe Mode and restarted again and ran a repair permissions on it. All seems to be ok for now BUT I haven't reopened iWeb for fear that that may be eating up what little memory is left AND then there is this OTHER issue of where these other 8 or so GB have gone to???? When I calculate Finder items in the HD they total 19.5 GB not the 27.64 that "Get Info" pulls up for it. One more note: I installed iLife '06 about a month ago... What is happening here?
PowerBook G4 17" Mac OS X (10.4.5)

Hi, O.
1. IMO, with only 2-3 GB of available (free) space, you're critically short of free disk space. Cache files and virtual memory swap files could readily and quickly consume that. See my "Problems from insufficient RAM and free hard disk space" FAQ.
2. A runaway process constantly writing to log files can chew up disk space. Check these Console logs for clues, specifically large blocks of repeating messages that recur at high-frequency. If you find such blocks, post some samples for diagnosis. Again, do not post the entire log or logs, just copy/paste samples of blocks of repeating messages that recur at high frequency.
Common causes of runaway processes writing to logs include software associated with Canon and HP scanners, software for HP All-In-One devices, and Adobe Acrobat version 7.x prior to version 7.0.5. Depending on the messages you post, I can give you specific actions to take if one of those apply.
3. See also my "Freeing Space on your Mac OS X startup disk" FAQ.
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X
Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
I may receive some form of compensation, financial or otherwise, from my recommendation or link.

HT1338 My Macbook Pro 13" says that I have no more memory in my startup disk. I've tried clearing files and folders and deleting applications but it still says that I have low memory. How do I fix it?

My MacBook Pro 13" says that I have no more memory in my startup disk. I have tried deleting applications, files, folders, and it still says I have low memory. What is taking up all that space?

First -- do the target disk backup. Somehow get a backup.
You might try booting to Single user mode: http://support.apple.com/kb/ht1492 and removing the files in the command line. When you put files in the trash, the space is still used up until the trash is emptied.
using rm command removes it totally. Just be very careful because you remove the wrong file, and you have to relad the system

"No enought room on startup disk for Application Memory" when using the Accelerate Framework

Dear colleagues,
I am running what I know is a large problem for a scientific application (tochnog) a finite element solver that runs from the Terminal. The application tries to solve 1,320,000 simultaneous linear equations. The problem starts when I use the Accelerate Framework as the Virtual Memory size jumps from 142 G to about 576 G after the library (LAPACK) is called to solve the system.It does not do it if I use a solver that does not calls LAPACK inside Accelerate.
The machine is a mac pro desktop with 8 GB of ram, the 2.66 GHz Quad-core Intel and the standard 640 GB hard drive. The system tells me that I have 487 GB available on hard drive.
The top instruction in Terminal reads VM 129G vsize when starting. When I run the finite element application once the LAPACK library in the Accelerate framework gets called, the Virtual Memory (VM) jumps to 563 G vsize.
After a short while, I get the "No enought room on startup disk for Application Memory error"
This is a screen capture of the application attempting to solve the problem using the LAPACK library inside the Accelerate framework: Here are the numbers as reported by the activity Monitor.
Tochnog Real Memory 6.68 GB
System Memory Free: 33.8 MB, Wired 378.8 MB, Active 5.06 GB, Inactive 2.53 GB, Used 7.96 GB.
VM size 567.52 GB, Page ins 270.8 MB, Page outs 108.2 MB, Swap used 505 MB
This is a screen copy of the same application solving the same problemwithout using the Accelerate framework.
Tochnog Real Memory 1.96 GB,
System Memory Free: 4.52 MB, Wired 382.1 MB, Active 2.69 GB, Inactive 416.2 GB, Used 3.47 GB.
VM size 148.60 GB, Page ins 288.8 MB, Page outs 108.2 MB, Swap used 2.5 MB
I can not understand the disparity in the behavior for the same case. As I said before, the only difference is the use of Accelerate in the first case. Also, as you can see, I thought that 8 GB of ram memory was a lot.
Your help will be greatly appreciated
Best regards,
F Lorenzo

The OP had posted this question in the iMac Intel forum.
I replied along similar lines, but suggested he repost this in the SL forum where I know there are usually several people who have a far better grasp of these issues than I.
I would be interested in getting their take on this.
Although, I think you are coming to the correct conclusion that there are not enough resources available for this process, I'm not certain that what you are saying on the way to that conclusion is correct. My understanding of VM is that it is the total theoretical demand on memory a process might make. It is not necessarily the actual or real world demand being made.
As such, this process is not actually demanding 568GB (rounded.) As evidence of that, you can see there is still memory available, albeit quite small, in the form of free memory of 33.8MB and inactive of 2.53GB (the GB for that figure, above, seems like it might be a typo, since for the process when not using Accelerate the reported figure for inactive was 416.2 GB -- surely impossible) and 7.96GB used. The process, itself, is using 6.68GB real memory.
In addition, I question whether the OP has misstated the 487GB free drive space. I think that might be the total drive capacity, not the free space.
My guess is that it is the combination of low available memory and low free drive space prompting this error.
From Dr. Smoke on VM:
it is possible that swap files could grow to the point where all free space on your disk is consumed by them. This can happen if you are very low on both RAM and free disk space.
https://discussions.apple.com/message/2232469?messageID=2232469&#2232469
This gets more to the actual intent of your question...
EDIT: Looks like some kind of glitch right now getting to the Dr. Smoke post.
Message was edited by: WZZZ
<Hyperlink Edited by Host>

When I open my iMac, I get this message - Your Mac OS X startup disk has no more space available for application memory. ???????

When I open my iMac, I get the following message : Your Mac OS X startup disk has no more space available for application memory. Then it says to quit applications not in usw and to close windows and remove files from startup disk. It lists Safari, email and Finder. I force a quit on all applications yet the same message comes up every time I open an application. What do I do to get rid of this once and for all? The computer is not even two years old and is only used for email and Safari. Help will be greatly appreciated,

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.

Getting messages "startup disk is full" and activity monitor is showing "syslog d" is using a lot of CPU. I'm planning on getting more memory for my late 2008 model Macbook but wondering if there's something that is causing problems that I can also fix.

I had closed out of all of my programs but heard the internal fans running so I checked the activity monitor. It shows syslog d as the top process using the CPU right now. I have no idea what that means.
I read a thread about the startup disk being full and how you can free up memory. I have an airport extreme so TimeCapsule is backing up everything. I do have a bunch of pictures on iPhoto on the laptop; could move those to another location but I'm a little gunshy. I know they are on the TimeCapsule but I would like to save them to a second place before deleting from laptop just to be sure. I went through several things yesterday and emptied trash, etc. I wasn't able to locate the hidden files that the thread about the startup disk being full was referencing --- they were talking about large emails that were causing processes to happen taking up the CPU.... I wasn't able to find out if that was the case for me.
Also I'm going to look into getting another 2MB of memory and installing it on the Macbook, so I can upgrade to the latest OS. Anyone have an idea if that is worth the $$$ over buying a new laptop? Or anyone have ideas as to where to buy memory, etc.
Any ideas - help!

Go step by step and test.
1. Start up in Safe Mode.
    http://support.apple.com/kb/PH11212
2. Empty Trash.
   http://support.apple.com/kb/PH13806
3. Disk space / Time Machine ?/ Local Snapshots
Local backups
   http://support.apple.com/kb/ht4878
4. Delete old iOS Devices Backup.
    iTunes > Preferences > Devices
    Highlight the old Backups , press “Delete Backup” and then “OK”.
    http://support.apple.com/kb/HT4946?viewlocale=en_US&locale=en_US
5. Re-index Macintosh HD.
    This will take a while. Wait until it is finished.
    System Preferences > Spotlight > Privacy
    http://support.apple.com/kb/ht2409

I just bought a new mac and need to clear the memory of my old one but i don't have a startup disk. how do i do this?

I just bought a new mac book pro and need to clear my old mac of it's contents to give it away--- I do not have my startup disk anymore. How can i completely delete my old mac's memory?

Erasing your drive:
Dragging the files to the Trash removes the references to them from the Directory. As has always been the tradition, the data blocks that held the actual data are not over-written, they are merely added to the free list for later re-use. Their original contents are still present.
Disk Utility "Erase" or "Partition" of a drive (which finishes in under a minute) also does not over-write the data blocks, but merely creates a new, empty directory.
To clear the data that may still be present (admittedly in a disorganized mess of unlinked blocks) you need to overwrite the data. Use the erase tab, then choose "Security Erase" Options, and overwrite once with Zeroes. This process can take several hours as it is -- if you insist on multiple passes, it can take days to complete, with little additional protection. Multiple passes is unnecessary unless your drive held Military Secrets.
When you have erased, be sure to install some version of Mac OS X -- a Mac with no obvious Operating software may be dead, and is much more likely to quickly become landfill.

Startup Disk Memory Error

I suddenly got a popup while playing Minecraft saying that my startup disk had run out of memory. Checking Macintosh HD's info, it was practically full even though the last time I downloaded anything I had over 70 GB free. Upon restart some of my System Preferences reset themselves (Dock, Mission Controls) as well as the icons I had on the dock. The only clue I have is from Console messages, since I didn't think of checking Activty Monitor...
Messages:
2/9/11 9:50:48.287 PM Google Chrome Helper: Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 9:50:48.287 PM [0x0-0xc00c].com.google.Chrome: 2011-09-02 21:50:48.285 Google Chrome Helper[22098:107] Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 9:50:49.364 PM [0x0-0xc00c].com.google.Chrome: [429:1287:30839981328405:ERROR:CONSOLE(6472)] "Uncaught TypeError: Cannot read property 'can_uninstall' of undefined", source: chrome://newtab/ (6472)
2/9/11 9:50:49.651 PM Google Chrome Helper: Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 9:50:49.652 PM [0x0-0xc00c].com.google.Chrome: 2011-09-02 21:50:49.649 Google Chrome Helper[22099:107] Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:02:08.586 PM Google Chrome Helper: Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:02:08.587 PM [0x0-0xc00c].com.google.Chrome: 2011-09-02 22:02:08.584 Google Chrome Helper[22575:107] Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:02:11.684 PM Google Chrome Helper: Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:02:11.685 PM [0x0-0xc00c].com.google.Chrome: 2011-09-02 22:02:11.682 Google Chrome Helper[22624:107] Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:27:24.705 PM Google Chrome Helper: Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:27:24.708 PM [0x0-0xc00c].com.google.Chrome: 2011-09-02 22:27:24.702 Google Chrome Helper[23539:107] Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:27:26.155 PM [0x0-0xc00c].com.google.Chrome: [429:1287:33036829445005:ERROR:CONSOLE(6472)] "Uncaught TypeError: Cannot read property 'can_uninstall' of undefined", source: chrome://newtab/ (6472)
2/9/11 10:27:26.384 PM [0x0-0xc00c].com.google.Chrome: 2011-09-02 22:27:26.381 Google Chrome Helper[23540:107] Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:27:26.383 PM Google Chrome Helper: Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:31:45.784 PM JavaApplicationStub: Failed to write public plist to URL file://localhost/Users/14tamh2/Library/Saved%20Application%20State/com.Mojang%2 0Specifications.Minecraft.Minecraft.savedState/windows.plist
2/9/11 10:49:24.328 PM com.apple.launchd.peruser.40829: (com.apple.quicklook.32bit) Unknown key for boolean: DisallowDataExecute
2/9/11 10:49:24.328 PM com.apple.launchd.peruser.40829: (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
2/9/11 10:49:24.334 PM com.apple.launchd.peruser.40829: (com.valvesoftware.steamclean) Bug: launchd_core_logic.c:5095 (24984):2
2/9/11 10:49:24.334 PM com.apple.launchd.peruser.40829: (com.valvesoftware.steamclean) Path monitoring failed on "/Volumes/FREECOM HDD/Applications (Under Macintosh HD)/Steam.app": No such file or directory
2/9/11 10:49:32.050 PM com.apple.dock.extra: Could not connect the action buttonPressed: to target of class NSApplication
2/9/11 10:49:32.052 PM com.apple.dock.extra: Could not connect the action buttonPressed: to target of class NSApplication
2/9/11 10:49:32.052 PM com.apple.dock.extra: Could not connect the action buttonPressed: to target of class NSApplication
2/9/11 10:49:32.054 PM com.apple.dock.extra: Could not connect the action buttonPressed: to target of class NSApplication
2/9/11 10:49:32.134 PM Google Chrome: Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:49:33.177 PM [0x0-0x9009].com.google.Chrome: [0902/224933:INFO:breakpad_mac.mm(89)] Breakpad disabled
2/9/11 10:49:33.262 PM [0x0-0x9009].com.google.Chrome: [315:1287:122260133854:ERROR:mac_util.mm(461)] Process launched at Login but can't access Login Item List.
2/9/11 10:49:35.852 PM Mail: Using V2 Layout
2/9/11 10:49:37.994 PM com.apple.fontd: FODBError: FODBReconcileWithAuxFile called: kAuxFileHeadersDontMatchErr
2/9/11 10:49:44.722 PM Google Chrome Helper: Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:49:44.723 PM [0x0-0x9009].com.google.Chrome: 2011-09-02 22:49:44.720 Google Chrome Helper[359:107] Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:49:48.701 PM [0x0-0x9009].com.google.Chrome: libprotobuf ERROR /b/build/slave/chrome-official-mac/build/src/third_party/protobuf/src/google/pr otobuf/message_lite.cc:123] Can't parse message of type "in_memory_url_index.InMemoryURLIndexCacheItem" because it is missing required fields: (cannot determine missing fields for lite message)
2/9/11 10:49:54.620 PM Google Chrome Helper: Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:49:54.621 PM [0x0-0x9009].com.google.Chrome: 2011-09-02 22:49:54.618 Google Chrome Helper[404:107] Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:50:09.024 PM com.apple.launchd.peruser.40829: (com.promethean.activmgr[522]) posix_spawn("/Applications/Promethean/ActivDriver/activmgr.app/Contents/MacOS/a ctivmgr", ...): No such file or directory
2/9/11 10:50:09.039 PM com.apple.launchd.peruser.40829: (com.promethean.activmgr[522]) Exited with code: 1
2/9/11 10:50:09.091 PM com.apple.launchd.peruser.40829: (com.fujixerox.hkg.AMDPClient[523]) open("/Applications/AMDPClient/Log/stdooutlog", ...): Permission denied
2/9/11 10:50:09.132 PM com.apple.launchd.peruser.40829: (com.fujixerox.hkg.AMDPClient[523]) open("/Applications/AMDPClient/Log/errorlog", ...): Permission denied
2/9/11 10:50:09.921 PM com.apple.launchd.peruser.40829: (com.valvesoftware.steamclean) Bug: launchd_core_logic.c:5095 (24984):2
2/9/11 10:50:09.921 PM com.apple.launchd.peruser.40829: (com.valvesoftware.steamclean) Path monitoring failed on "/Volumes/FREECOM HDD/Applications (Under Macintosh HD)/Steam.app": No such file or directory
2/9/11 10:50:10.996 PM Adobe Acrobat Updater Helper: Adobe Acrobat Updater encountered errorCode 1537
2/9/11 10:50:11.000 PM Adobe Acrobat Updater Helper: Adobe Acrobat Updater encountered errorCode 1525
2/9/11 10:50:12.422 PM [0x0-0x21021].com.apple.JarLauncher: 02-Sep-2011 22:50:12 java.util.jar.Attributes read
2/9/11 10:50:12.422 PM [0x0-0x21021].com.apple.JarLauncher: WARNING: Duplicate name in Manifest: SHA1-Digest.
2/9/11 10:50:12.422 PM [0x0-0x21021].com.apple.JarLauncher: Ensure that the manifest does not have duplicate entries, and
2/9/11 10:50:12.422 PM [0x0-0x21021].com.apple.JarLauncher: that blank lines separate individual sections in both your
2/9/11 10:50:12.422 PM [0x0-0x21021].com.apple.JarLauncher: manifest and in the META-INF/MANIFEST.MF entry in the jar file.
2/9/11 10:50:12.422 PM [0x0-0x21021].com.apple.JarLauncher: 02-Sep-2011 22:50:12 java.util.jar.Attributes read
2/9/11 10:50:12.422 PM [0x0-0x21021].com.apple.JarLauncher: WARNING: Duplicate name in Manifest: SHA1-Digest.
2/9/11 10:50:12.422 PM [0x0-0x21021].com.apple.JarLauncher: Ensure that the manifest does not have duplicate entries, and
2/9/11 10:50:12.422 PM [0x0-0x21021].com.apple.JarLauncher: that blank lines separate individual sections in both your
2/9/11 10:50:12.422 PM [0x0-0x21021].com.apple.JarLauncher: manifest and in the META-INF/MANIFEST.MF entry in the jar file.
2/9/11 10:50:12.422 PM [0x0-0x21021].com.apple.JarLauncher: 02-Sep-2011 22:50:12 java.util.jar.Attributes read
2/9/11 10:50:12.422 PM [0x0-0x21021].com.apple.JarLauncher: WARNING: Duplicate name in Manifest: SHA1-Digest.
2/9/11 10:50:12.422 PM [0x0-0x21021].com.apple.JarLauncher: Ensure that the manifest does not have duplicate entries, and
2/9/11 10:50:12.422 PM [0x0-0x21021].com.apple.JarLauncher: that blank lines separate individual sections in both your
2/9/11 10:50:12.422 PM [0x0-0x21021].com.apple.JarLauncher: manifest and in the META-INF/MANIFEST.MF entry in the jar file.
2/9/11 10:50:12.426 PM [0x0-0x21021].com.apple.JarLauncher: 02-Sep-2011 22:50:12 java.util.jar.Attributes read
2/9/11 10:50:12.426 PM [0x0-0x21021].com.apple.JarLauncher: WARNING: Duplicate name in Manifest: SHA1-Digest.
2/9/11 10:50:12.426 PM [0x0-0x21021].com.apple.JarLauncher: Ensure that the manifest does not have duplicate entries, and
2/9/11 10:50:12.426 PM [0x0-0x21021].com.apple.JarLauncher: that blank lines separate individual sections in both your
2/9/11 10:50:12.426 PM [0x0-0x21021].com.apple.JarLauncher: manifest and in the META-INF/MANIFEST.MF entry in the jar file.
2/9/11 10:50:12.427 PM [0x0-0x21021].com.apple.JarLauncher: 02-Sep-2011 22:50:12 java.util.jar.Attributes read
2/9/11 10:50:12.427 PM [0x0-0x21021].com.apple.JarLauncher: WARNING: Duplicate name in Manifest: SHA1-Digest.
2/9/11 10:50:12.427 PM [0x0-0x21021].com.apple.JarLauncher: Ensure that the manifest does not have duplicate entries, and
2/9/11 10:50:12.427 PM [0x0-0x21021].com.apple.JarLauncher: that blank lines separate individual sections in both your
2/9/11 10:50:12.427 PM [0x0-0x21021].com.apple.JarLauncher: manifest and in the META-INF/MANIFEST.MF entry in the jar file.
2/9/11 10:50:12.427 PM [0x0-0x21021].com.apple.JarLauncher: 02-Sep-2011 22:50:12 java.util.jar.Attributes read
2/9/11 10:50:12.427 PM [0x0-0x21021].com.apple.JarLauncher: WARNING: Duplicate name in Manifest: SHA1-Digest.
2/9/11 10:50:12.427 PM [0x0-0x21021].com.apple.JarLauncher: Ensure that the manifest does not have duplicate entries, and
2/9/11 10:50:12.427 PM [0x0-0x21021].com.apple.JarLauncher: that blank lines separate individual sections in both your
2/9/11 10:50:12.427 PM [0x0-0x21021].com.apple.JarLauncher: manifest and in the META-INF/MANIFEST.MF entry in the jar file.
2/9/11 10:50:15.559 PM [0x0-0x21021].com.apple.JarLauncher: 02-Sep-2011 22:50:15 java.util.jar.Attributes read
2/9/11 10:50:15.559 PM [0x0-0x21021].com.apple.JarLauncher: WARNING: Duplicate name in Manifest: SHA1-Digest.
2/9/11 10:50:15.559 PM [0x0-0x21021].com.apple.JarLauncher: Ensure that the manifest does not have duplicate entries, and
2/9/11 10:50:15.559 PM [0x0-0x21021].com.apple.JarLauncher: that blank lines separate individual sections in both your
2/9/11 10:50:15.559 PM [0x0-0x21021].com.apple.JarLauncher: manifest and in the META-INF/MANIFEST.MF entry in the jar file.
2/9/11 10:50:15.561 PM [0x0-0x21021].com.apple.JarLauncher: 02-Sep-2011 22:50:15 java.util.jar.Attributes read
2/9/11 10:50:15.561 PM [0x0-0x21021].com.apple.JarLauncher: WARNING: Duplicate name in Manifest: SHA1-Digest.
2/9/11 10:50:15.561 PM [0x0-0x21021].com.apple.JarLauncher: Ensure that the manifest does not have duplicate entries, and
2/9/11 10:50:15.561 PM [0x0-0x21021].com.apple.JarLauncher: that blank lines separate individual sections in both your
2/9/11 10:50:15.561 PM [0x0-0x21021].com.apple.JarLauncher: manifest and in the META-INF/MANIFEST.MF entry in the jar file.
2/9/11 10:50:15.563 PM [0x0-0x21021].com.apple.JarLauncher: 02-Sep-2011 22:50:15 java.util.jar.Attributes read
2/9/11 10:50:15.563 PM [0x0-0x21021].com.apple.JarLauncher: WARNING: Duplicate name in Manifest: SHA1-Digest.
2/9/11 10:50:15.563 PM [0x0-0x21021].com.apple.JarLauncher: Ensure that the manifest does not have duplicate entries, and
2/9/11 10:50:15.563 PM [0x0-0x21021].com.apple.JarLauncher: that blank lines separate individual sections in both your
2/9/11 10:50:15.563 PM [0x0-0x21021].com.apple.JarLauncher: manifest and in the META-INF/MANIFEST.MF entry in the jar file.
2/9/11 10:50:15.974 PM [0x0-0x21021].com.apple.JarLauncher: 02-Sep-2011 22:50:15 org.apache.axis.utils.JavaUtils isAttachmentSupported
2/9/11 10:50:15.974 PM [0x0-0x21021].com.apple.JarLauncher: WARNING: Unable to find required classes (javax.activation.DataHandler and javax.mail.internet.MimeMultipart). Attachment support is disabled.
2/9/11 10:50:16.211 PM [0x0-0x21021].com.apple.JarLauncher: Listening on port 8000
2/9/11 10:51:56.022 PM Google Chrome Helper: Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:51:56.022 PM [0x0-0x9009].com.google.Chrome: 2011-09-02 22:51:56.020 Google Chrome Helper[638:107] Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:52:06.976 PM Google Chrome Helper: Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:52:06.977 PM [0x0-0x9009].com.google.Chrome: 2011-09-02 22:52:06.975 Google Chrome Helper[641:107] Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:52:08.823 PM Google Chrome Helper: Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:52:08.824 PM [0x0-0x9009].com.google.Chrome: 2011-09-02 22:52:08.821 Google Chrome Helper[642:107] Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:52:09.894 PM Google Chrome Helper: Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:52:09.895 PM [0x0-0x9009].com.google.Chrome: 2011-09-02 22:52:09.892 Google Chrome Helper[643:107] Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:52:13.062 PM Google Chrome Helper: Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:52:13.073 PM [0x0-0x9009].com.google.Chrome: 2011-09-02 22:52:13.060 Google Chrome Helper[645:c03] Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:52:19.164 PM Google Chrome Helper: Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:52:19.164 PM [0x0-0x9009].com.google.Chrome: 2011-09-02 22:52:19.162 Google Chrome Helper[646:107] Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:52:21.059 PM Google Chrome Helper: Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:52:21.059 PM [0x0-0x9009].com.google.Chrome: 2011-09-02 22:52:21.057 Google Chrome Helper[647:107] Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:52:31.322 PM Google Chrome Helper: Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:52:31.322 PM [0x0-0x9009].com.google.Chrome: 2011-09-02 22:52:31.320 Google Chrome Helper[650:107] Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:53:13.262 PM helpd: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
2/9/11 10:53:13.263 PM helpd: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
2/9/11 10:55:55.703 PM hiutil: nameLen <= 0!
2/9/11 10:55:55.704 PM com.apple.helpd: 2011-09-02 22:55:55.701 hiutil[838:2007] nameLen <= 0!
2/9/11 10:55:55.704 PM hiutil: nameLen <= 0!
2/9/11 10:55:55.704 PM com.apple.helpd: 2011-09-02 22:55:55.703 hiutil[838:2007] nameLen <= 0!
2/9/11 10:57:21.234 PM Google Chrome Helper: Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:57:21.235 PM [0x0-0x9009].com.google.Chrome: 2011-09-02 22:57:21.220 Google Chrome Helper[890:107] Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:57:29.244 PM Google Chrome Helper: Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:57:29.245 PM [0x0-0x9009].com.google.Chrome: 2011-09-02 22:57:29.241 Google Chrome Helper[891:107] Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:57:32.710 PM Google Chrome Helper: Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:57:32.711 PM [0x0-0x9009].com.google.Chrome: 2011-09-02 22:57:32.705 Google Chrome Helper[892:107] Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:57:37.292 PM Google Chrome Helper: Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:57:37.292 PM [0x0-0x9009].com.google.Chrome: 2011-09-02 22:57:37.290 Google Chrome Helper[893:107] Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:57:38.182 PM Google Chrome Helper: Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:57:38.185 PM [0x0-0x9009].com.google.Chrome: 2011-09-02 22:57:38.180 Google Chrome Helper[895:107] Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:57:39.782 PM Google Chrome Helper: Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:57:39.783 PM [0x0-0x9009].com.google.Chrome: 2011-09-02 22:57:39.739 Google Chrome Helper[897:107] Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:57:40.421 PM Google Chrome Helper: Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:57:40.421 PM [0x0-0x9009].com.google.Chrome: 2011-09-02 22:57:40.419 Google Chrome Helper[898:107] Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:57:41.333 PM Google Chrome Helper: Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:57:41.334 PM [0x0-0x9009].com.google.Chrome: 2011-09-02 22:57:41.316 Google Chrome Helper[899:107] Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:57:44.765 PM Google Chrome Helper: Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:57:44.766 PM [0x0-0x9009].com.google.Chrome: 2011-09-02 22:57:44.763 Google Chrome Helper[900:107] Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:57:50.595 PM Google Chrome Helper: Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:57:50.596 PM [0x0-0x9009].com.google.Chrome: 2011-09-02 22:57:50.591 Google Chrome Helper[933:107] Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:58:10.656 PM Google Chrome Helper: Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:58:10.656 PM [0x0-0x9009].com.google.Chrome: 2011-09-02 22:58:10.654 Google Chrome Helper[936:107] Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 10:58:14.493 PM [0x0-0x9009].com.google.Chrome: Google Chrome Helper(936,0xb0b0d000) malloc: *** error for object 0x38bf410: double free
2/9/11 10:58:14.493 PM [0x0-0x9009].com.google.Chrome: *** set a breakpoint in malloc_error_break to debug
2/9/11 10:58:14.496 PM [0x0-0x9009].com.google.Chrome: Google Chrome Helper(936,0xb0b0d000) malloc: *** error for object 0x3a9d170: double free
2/9/11 10:58:14.496 PM [0x0-0x9009].com.google.Chrome: *** set a breakpoint in malloc_error_break to debug
2/9/11 10:58:14.500 PM [0x0-0x9009].com.google.Chrome: Google Chrome Helper(936,0xb0b0d000) malloc: *** error for object 0x38bf3f0: double free
2/9/11 10:58:14.500 PM [0x0-0x9009].com.google.Chrome: *** set a breakpoint in malloc_error_break to debug
2/9/11 11:00:15.289 PM Google Chrome Helper: Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
2/9/11 11:00:15.289 PM [0x0-0x9009].com.google.Chrome: 2011-09-02 23:00:15.287 Google Chrome Helper[1006:107] Unsure about the internals of CFAllocator but going to patch them anyway. Watch out for crashes inside of CFAllocatorAllocate.
What I find odd is all of the Google Chrome Helper messages, but I have no idea at all what caused it.

Not to mention, after restarting my startup disk it returned to normal.

I'm trying to up grade the os but I keep getting the startup disk is full I ordered more memory I was told this will not help. What do I do?

I'm trying to up grade the os but I keep getting the startup disk is full I ordered more memory I was told this will not help. What do I do?

I think as drive capacities increase, the old 10-15% becomes less accurate. The amount of free space you need doesn't really have anything to do with the drive size. So, increasing your drive size shouldn't mean that you need to have more free GB (which using a % of drive space would mean). You need free space to accommodate page outs (the amount of which would depend on how much RAM you have installed and how memory intensive the applications are), sleep images (again, this would max out at your total amount of RAM), and a bit to minimize fragmentation.
With desktop drives commonly in the 2TB range today, it is certainly not necessary to have 200GB+ free in order to maintain proper operation. I generally find about 30GB to be the minimum I'm comfortable with. Mind you, I pretty much always have way more than that available. But, if I'm working on a system and the amount of free space is at least 30GB, I would generally not site drive space as the cause of any performance issues. I'd say that 30GB is a minimum for a stable system (with 8GB or RAM installed). Of course at that amount, you would still need to free up space if you were to want to install or download any significant amount of data.
With servers being more likely to run into the 16GB of RAM range, more storage would be necessary. Most servers should be well stocked with storage, but the actual needs would vary greatly depending on what's being "served".
The 10-15% thing came about when we used to talk about drive capacities in hundreds of MBs and RAM in terms of KB (not MB and certainly not GB). More drive space is always a good thing, but as drive capacities continue to sky rocket, we don't need to dedicate larger amounts of storage on systems with the same specifications. A set amount of space is required for proper operation regardless of the capacity of the drive installed.

Startup disk/memory problem

Having an annoying issue. Over time as I use my computer the activity monitor shows memory (ram) decreases. For example, I surf the internet for 1 -2 hours, the available memory slowly decreases until I get an error telling me to force quit safari due to low memory. Safari also won't store passwords/logins, and sporadically takes history. Often, I can't take a screen grab and the error box says I don't have permission, but it works sometimes. The same problem when I'm trying to download something, I get an error that I can't write the file. Crashes happen a lot when I try to print something or open a file in word or adobe reader. I backed up all my files and did a fresh install of the os using the disk provided. The problems persist, even with over 100 gb free...double checked this with disk inventory x. I've repaired/restored permissions in disk utility. Most of the time a shut down (not restart), and starting up again fixes the problems for a while. I've searched google and read a few forums about similar problems, nothing has fixed this. Any thoughts?

A download stopped right at the end and it could not write it. I tried taking a screen grab of the messages, but it crashed. It just kept repeating something about being unable to log messages hundreds of times. The following was in the system log at the time around the download. Since the download started this time without a problem, the computer was operating fine until the end of the download.
May 13 01:44:51 virinder-sidhus-macbook-pro /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framewo rk/Support/ATSServer[87]: FOExceptionMainHandler caught a fatal exception at 0x002b4344
May 13 01:44:51 virinder-sidhus-macbook-pro /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framewo rk/Support/ATSServer[87]: FOExceptionMainHandler caught a fatal exception at 0x002b4344
May 13 01:45:21: --- last message repeated 3 times ---
May 13 01:45:26 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:45:26 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:45:27: --- last message repeated 1 time ---
May 13 01:45:27 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:45:27 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:45:27: --- last message repeated 1 time ---
May 13 01:45:27 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:45:27 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:45:27: --- last message repeated 1 time ---
May 13 01:45:27 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:45:27 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:45:27: --- last message repeated 1 time ---
May 13 01:45:27 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:45:27 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:45:27: --- last message repeated 1 time ---
May 13 01:45:27 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:45:27 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:45:28: --- last message repeated 1 time ---
May 13 01:45:28 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:45:28 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:45:28: --- last message repeated 1 time ---
May 13 01:45:28 virinder-sidhus-macbook-pro mdworker[520]: Expected bookmark file to be a CFDictionary but it isn't. Aborting.
May 13 01:45:28 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:45:28 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:45:28: --- last message repeated 1 time ---
May 13 01:45:28 virinder-sidhus-macbook-pro mdworker[520]: Expected bookmark file to be a CFDictionary but it isn't. Aborting.
May 13 01:47:52 virinder-sidhus-macbook-pro /usr/sbin/ocspd[546]: starting
May 13 01:51:28 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:51:28 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:51:29: --- last message repeated 1 time ---
May 13 01:51:29 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:51:29 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:51:29: --- last message repeated 1 time ---
May 13 01:51:29 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:51:29 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:51:29: --- last message repeated 1 time ---
May 13 01:51:29 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:51:29 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:51:29: --- last message repeated 1 time ---
May 13 01:51:29 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:51:29 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:51:32: --- last message repeated 1 time ---
May 13 01:51:32 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:51:32 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:51:33: --- last message repeated 1 time ---
May 13 01:51:33 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:51:33 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:51:33: --- last message repeated 1 time ---
May 13 01:51:33 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:51:33 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:51:33: --- last message repeated 1 time ---
May 13 01:51:33 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:51:33 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:51:33: --- last message repeated 1 time ---
May 13 01:51:33 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:51:33 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:51:33: --- last message repeated 1 time ---
May 13 01:51:33 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:51:33 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:51:59: --- last message repeated 1 time ---
May 13 01:51:59 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:51:59 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:52:02: --- last message repeated 1 time ---
May 13 01:52:02 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:52:02 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:52:02: --- last message repeated 1 time ---
May 13 01:52:02 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:52:02 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:52:02: --- last message repeated 1 time ---
May 13 01:52:02 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:52:02 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:52:02: --- last message repeated 1 time ---
May 13 01:52:02 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:52:02 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:52:03: --- last message repeated 1 time ---
May 13 01:52:03 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:52:03 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:52:03: --- last message repeated 1 time ---
May 13 01:52:03 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:52:03 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:52:33: --- last message repeated 1 time ---
May 13 01:58:17 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:58:17 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:58:18: --- last message repeated 1 time ---
May 13 01:58:18 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:58:18 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:58:18: --- last message repeated 1 time ---
May 13 01:58:18 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:58:18 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:58:19: --- last message repeated 1 time ---
May 13 01:58:19 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:58:19 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:58:19: --- last message repeated 1 time ---
May 13 01:58:19 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:58:19 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:58:21: --- last message repeated 1 time ---
May 13 01:58:21 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:58:21 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:58:21: --- last message repeated 1 time ---
May 13 01:58:21 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:58:21 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:58:21: --- last message repeated 1 time ---
May 13 01:58:21 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:58:21 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:58:21: --- last message repeated 1 time ---
May 13 01:58:21 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:58:21 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:58:21: --- last message repeated 1 time ---
May 13 01:58:21 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:58:21 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:58:21: --- last message repeated 1 time ---
May 13 01:58:21 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:58:21 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:58:21: --- last message repeated 1 time ---
May 13 01:58:21 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:58:21 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:58:21: --- last message repeated 1 time ---
May 13 01:58:21 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:58:21 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:58:21: --- last message repeated 1 time ---
May 13 01:58:21 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:58:21 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:58:22: --- last message repeated 1 time ---
May 13 01:58:22 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:58:22 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:58:22: --- last message repeated 1 time ---
May 13 01:58:22 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:58:22 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:58:22: --- last message repeated 1 time ---
May 13 01:58:22 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:58:22 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:58:22: --- last message repeated 1 time ---
May 13 01:58:22 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:58:22 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:58:38: --- last message repeated 1 time ---
May 13 01:58:38 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:58:38 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:58:38: --- last message repeated 1 time ---
May 13 01:58:38 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:58:38 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:58:38: --- last message repeated 1 time ---
May 13 01:58:38 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:58:38 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:58:38: --- last message repeated 1 time ---
May 13 01:58:38 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 01:58:38 virinder-sidhus-macbook-pro kernel[0]:
May 13 01:59:08: --- last message repeated 1 time ---
May 13 02:03:39 virinder-sidhus-macbook-pro ntpd[14]: time reset +0.922684 s
May 13 02:07:48 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 02:07:48 virinder-sidhus-macbook-pro kernel[0]:
May 13 02:07:49: --- last message repeated 1 time ---
May 13 02:07:49 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 02:07:49 virinder-sidhus-macbook-pro kernel[0]:
May 13 02:07:49: --- last message repeated 1 time ---
May 13 02:07:49 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 02:07:49 virinder-sidhus-macbook-pro kernel[0]:
May 13 02:07:49: --- last message repeated 1 time ---
May 13 02:07:49 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 02:07:49 virinder-sidhus-macbook-pro kernel[0]:
May 13 02:08:19: --- last message repeated 1 time ---
May 13 02:12:12 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 02:12:12 virinder-sidhus-macbook-pro kernel[0]:
May 13 02:12:12: --- last message repeated 1 time ---
May 13 02:12:12 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 02:12:12 virinder-sidhus-macbook-pro kernel[0]:
May 13 02:12:12: --- last message repeated 1 time ---
May 13 02:12:12 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 02:12:12 virinder-sidhus-macbook-pro kernel[0]:
May 13 02:12:12: --- last message repeated 1 time ---
May 13 02:12:12 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 02:12:12 virinder-sidhus-macbook-pro kernel[0]:
May 13 02:12:18: --- last message repeated 1 time ---
May 13 02:12:18 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 02:12:18 virinder-sidhus-macbook-pro kernel[0]:
May 13 02:12:18: --- last message repeated 1 time ---
May 13 02:12:18 virinder-sidhus-macbook-pro kernel[0]: jnl: unknown-dev: do_jnl_io: strategy err 0x5
May 13 02:12:18 virinder-sidhus-macbook-pro kernel[0]: jnl: unknown-dev: end_transaction: only wrote 0 of 250368 bytes to the journal!
May 13 02:19:44 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 02:19:44 virinder-sidhus-macbook-pro kernel[0]:
May 13 02:19:44: --- last message repeated 1 time ---
May 13 02:19:44 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 02:19:45 virinder-sidhus-macbook-pro kernel[0]:
May 13 02:19:45: --- last message repeated 1 time ---
May 13 02:19:45 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 02:19:45 virinder-sidhus-macbook-pro kernel[0]:
May 13 02:19:45: --- last message repeated 1 time ---
May 13 02:19:45 virinder-sidhus-macbook-pro kernel[0]: disk0s2: I/O error.
May 13 02:19:45 virinder-sidhus-macbook-pro kernel[0]:

Startup disk memory full

I am getting a message saying that my startup disk is almost full so the file I'm trying to save cannot be saved.
The weird thing is that I am trying to save a 2MB file and I have still 94GB of free space in my startup disk!!!
Does anyone know what could be happening here?
Thanks,
Cantautor

Scan your drive with WhatSize once and see if you can see what's eating up your disk space.
http://www.id-design.com/Software/WhatSize/
Pay attention to these files:
/private/var/vm
/private/var/log
/Volumes
The /private/var/vm directory contains the swapfiles used by virutal memory. New ones are made as more data is swapped from RAM to the hard drive. The entire process of creating them begins at each reboot or restart. Check the total size of all the swapfiles, right after you boot, and as the disk fills up. Swapfiles are used by virtual memory. The first two are 64MB, then each new one is twice the size of the preceeding one (128MB, 256MB, 512MB...).
If you do not run the daily, weekly, and monthly maintenance routines (either by using a utility, or by running the commands sudo perioidic daily, sudo perioidc weekly, and sudo periodic monthly in Terminal), you will accumulate too many logs. If an error is occurring frequently and is being logged, you can have a very large file at /private/var/log/system.log. I recently saw mention of a system.log file that was larger than 40 GB.
-Bmer
Mac Owners Support Group
Join Us @ MacOSG.com
IiTunes: MacOSG Podcast
 An Apple User Group 
Note: I receive no compensation for product endorsements.

I got a Force Quit error box telling me to quit two applications because my startup disk was out of memory to run applications. What is this?

I have a MacBook (mid-2007) with 2gb ram (max allowed) and recently upgraded to a 750 GB hard drive. And I have over 590 GB free Tonight I got a popup box requiring me to force quit my applications because I had run out of room on my startup disk. I was only running the finder, I-clean memory, Safari and mail at the time. I have been running that combination of programs forever and have never encountered this message. What is going on?

KKDani wrote:
Do I delete things...?
Yes.
Use this as a guide:
http://pondini.org/OSX/DiskSpace.html
Ciao.

New MacAir error states "your Mac OSX startup disk has no more space available for application memory" All I have added is MS Office

My new Mac Air states that my " Mac OSX startup disk has no more space available for application memory" and wants to force quit Safari. I have only added MS Office to the computer and Carbonite. Any suggestions?

Select the icon of your startup volume ("Macintosh HD," unless you renamed it) in the Finder and open the Info window. What value is shown for Available (space)?

"Startup disk out of application memory" error

A friend was copying a large block of files from his startup disk to an external backup drive when a message popped up in the Finder warning that "the startup disk has no more space available for application memory". The message went on to list the open apps, including the Finder. Everything slowed down when the computer was used for anything other than the copying operation that was already in progress.
The computer is a 3.06GHz i3 iMac with 8GB RAM running Snow Leopard 10.6.8. I've never seen this message before or even heard of this message. Can anyone tell me what it means and what, if anything, my friend needs to do about it?

Thanks, Klaus. No one in that discussion thread actually explains the meaning of this warning or what might cause it. It's quite possible that my friend will never see the same warning again, but it would be good to know what triggered the warning and what should be done about it beyond restarting the computer to delete the swap files.

Low memory startup disk

Similar Messages

Maybe you are looking for